Message135010
> 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:22 | neologix | set | recipients:
+ neologix, pitrou, flox, dmalcolm, kaifeng |
2011-05-02 21:59:21 | neologix | set | messageid: <1304373561.81.0.199103823851.issue11849@psf.upfronthosting.co.za> |
2011-05-02 21:59:21 | neologix | link | issue11849 messages |
2011-05-02 21:59:21 | neologix | create | |
|