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: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Sun, 26 May 2013 17:39:54 +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 #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.