This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug stdio/4099] Overly agressive caching by stream i/o functions.


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]