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 kristjan.jonsson, larry, neologix, pitrou, tim.peters, vstinner
Date 2014-04-16.07:03:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3xixSOWfxt=UX1+FoCmuoTgznbmihLibGsVgkZ=Jt+eQ@mail.gmail.com>
In-reply-to <1397581194.56.0.274160051799.issue21220@psf.upfronthosting.co.za>
Content
> In Python 3, arenas are allocated using mmap(), so wherever the arena ends up in the address space shouldn't matter, should it?

Indeed, although the effect on cache locality isn't clear.
Also, I don't think this solves the problem of having a single object
allocated inside a high address arena preventing the heap from
shrinking (which was the original reason for having the arenas
allocated by mmap).

Anyway, we can only go that far with reference counting (I mean that
you'd need a proper moving garbage collector for this).
History
Date User Action Args
2014-04-16 07:03:37neologixsetrecipients: + neologix, tim.peters, pitrou, kristjan.jonsson, vstinner, larry
2014-04-16 07:03:37neologixlinkissue21220 messages
2014-04-16 07:03:37neologixcreate