This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug stdio/4099] Overly agressive caching by stream i/o functions.
- From: "green at linuxhacker dot ru" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Sun, 26 May 2013 16:31:23 +0000
- Subject: [Bug stdio/4099] Overly agressive caching by stream i/o functions.
- Auto-submitted: auto-generated
- References: <bug-4099-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=4099
--- Comment #6 from Oleg Drokin <green at linuxhacker dot ru> ---
I would mostly agree with Rich that it does not make much sense to do a lot of
caching for reading. Bulk of the benefit is realized once 4K or so is read.
Then, seeks don't need to "pre-buffer" as much data as well which is a plus too
(and a lot of people consider seek to be a free operation). This should not
even be used when doing O_SYNC (that's where I disagree).
On the other hand, using full st_blksize for write caching makes total sense
and I see little to be gained from removing this, filesystems that advertize
bigger st_blksize would definitely get a big benefit out of it, allowing more
optimal write placing or whatever other benefits there might be from it's
perspective.
--
You are receiving this mail because:
You are on the CC list for the bug.