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 tim.peters
Recipients loewis, pitrou, sable, tim.peters
Date 2008-09-08.00:52:06
SpamBayes Score 2.0899037e-08
Marked as misclassified No
Message-id <>
> Anything in obmalloc that is not arena space should continue to come
> from malloc, I believe.

Sorry, but I don't understand why arena space should be different.  If a
platform's libc implementers think mmap should be used to obtain 256KB
chunks (i.e., arenas), then surely they implement the platform malloc to
defer to mmap in such cases.  If they don't but "should", then bugging
the platform vendor to improve the system malloc in this respect is the
best idea (then all apps on the platform benefit, and Python stays simpler).

OTOH, if for some compelling reason it's believed Python knows better
than platform vendors, then obmalloc should be uglied-up on all paths to
make the enlightened choice.
Date User Action Args
2008-09-08 00:52:07tim.peterssetrecipients: + tim.peters, loewis, pitrou, sable
2008-09-08 00:52:07tim.peterssetmessageid: <>
2008-09-08 00:52:07tim.peterslinkissue3526 messages
2008-09-08 00:52:06tim.peterscreate