Message 217242 - Python tracker

Message217242

Author	neologix
Recipients	josh.r, jtaylor, neologix, njs, pitrou, skrah, vstinner
Date	2014-04-27.08:30:35
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAH_1eM346H24rPVVZU8us88tZ7op9Azw_3KsOpZk1zD4q4DK8Q@mail.gmail.com>
In-reply-to	<1398557150.79.0.531385722906.issue21233@psf.upfronthosting.co.za>

Content
> I read again some remarks about alignement, it was suggested to provide allocators providing an address aligned to a requested alignement. This topic was already discussed in #18835. The alignement issue is really orthogonal to the calloc one, so IMO this shouldn't be discussed here (and FWIW I don't think we should expose those: alignement only matters either for concurrency or SIMD instructions, and I don't think we should try to standardize this kind of API, it's way to special-purpose (then we'd have to think about huge pages, etc...). Whereas calloc is a simple and immediately useful addition, not only for Numpy but also CPython).

Content

> I read again some remarks about alignement, it was suggested to provide allocators providing an address aligned to a requested alignement. This topic was already discussed in #18835.

The alignement issue is really orthogonal to the calloc one, so IMO
this shouldn't be discussed here (and FWIW I don't think we should
expose those: alignement only matters either for concurrency or SIMD
instructions, and I don't think we should try to standardize this kind
of API, it's way to special-purpose (then we'd have to think about
huge pages, etc...). Whereas calloc is a simple and immediately useful
addition, not only for Numpy but also CPython).

History
Date	User	Action	Args
2014-04-27 08:30:36	neologix	set	recipients: + neologix, pitrou, vstinner, njs, skrah, jtaylor, josh.r
2014-04-27 08:30:36	neologix	link	issue21233 messages
2014-04-27 08:30:35	neologix	create