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 njs
Recipients benjamin.peterson, neologix, njs, pitrou, rhettinger, skrah, tim.peters, trent, vstinner, wscullin, xdegaye
Date 2017-10-31.18:26:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> But since no fast (kernel-zeroed) aligned_calloc() exists, I must use memset() anyway. 

For large allocations, you'll probably be better off implementing your own aligned allocator on top of calloc than implementing your own calloc on top of an aligned allocator. (It's O(1) overhead versus O(n).) And once you're doing that you might want to use the same code for regular allocations too, so that you don't need to keep track of whether each memory block used aligned_calloc or aligned_malloc and can treat them the same... Depends on your exact circumstances.
Date User Action Args
2017-10-31 18:26:17njssetrecipients: + njs, tim.peters, rhettinger, pitrou, vstinner, benjamin.peterson, trent, skrah, neologix, xdegaye, wscullin
2017-10-31 18:26:17njssetmessageid: <>
2017-10-31 18:26:17njslinkissue18835 messages
2017-10-31 18:26:17njscreate