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 #7 from Rich Felker <bugdal at aerifal dot cx> ---
> 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.

This only makes sense if write() actually writes something to disk. It doesn't.
It (conceptually) memcpy's from a userspace buffer to the kernel's cache
buffers. So there's no reason to think the optimal write() size has anything to
do with the filesystem's block size.

-- 
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]