This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients dmalcolm, flox, kaifeng, neologix, pitrou
Date 2011-05-02.21:59:20
SpamBayes Score 5.15982e-09
Marked as misclassified No
Message-id <>
> I guess the final patch will have to guard the mallopt() call with some #ifdef?

Yes. See attached patch pymalloc_frag.diff
It's the first time I'm playing with autotools, so please review this part really carefully ;-)

> (also, I suppose a portable solution would have to call mmap() ourselves
> for allocation of arenas, but that would probably be a bit more involved)

Yes. But since it probably only affects glibc/eglibc malloc versions, I guess that target implementations are likely to provide mallopt(M_MMAP_THRESHOLD).
Also, performing an anonymous mappings varies even among Unices (the mmapmodule code is scary). I'm not talking about Windows, which I don't know at all.
Date User Action Args
2011-05-02 21:59:22neologixsetrecipients: + neologix, pitrou, flox, dmalcolm, kaifeng
2011-05-02 21:59:21neologixsetmessageid: <>
2011-05-02 21:59:21neologixlinkissue11849 messages
2011-05-02 21:59:21neologixcreate