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 demian.brecht
Recipients Claudiu.Popa, demian.brecht, vstinner
Date 2014-06-20.19:56:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403294209.88.0.941500152761.issue21790@psf.upfronthosting.co.za>
In-reply-to
Content
I very well could be missing something here (and, admittedly, my OS knowledge is rusty at best), but for the most part, page sizes are 4096, except for SPARC, which is 8192.

> So your page double the number of calls to read(), right?

No. read() is called until EOF. I'm assuming that 8192 may have been used to accommodate worst case architecture?

I'd have to dig through the C side of things (which I haven't done yet) to see what's going on down at that level, but my assumption is that it's allocating 8192 bytes for each read. Should EOF be reached with <= 1 page filled, it'd result in a wasted page.

Far from the end of the world, but just something I noticed in passing.
History
Date User Action Args
2014-06-20 19:56:49demian.brechtsetrecipients: + demian.brecht, vstinner, Claudiu.Popa
2014-06-20 19:56:49demian.brechtsetmessageid: <1403294209.88.0.941500152761.issue21790@psf.upfronthosting.co.za>
2014-06-20 19:56:49demian.brechtlinkissue21790 messages
2014-06-20 19:56:49demian.brechtcreate