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: "neleai at seznam dot cz" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Sat, 25 May 2013 19:20:33 +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 #3 from Ondrej Bilka <neleai at seznam dot cz> ---
On Sat, May 25, 2013 at 12:55:48PM +0000, bugdal at aerifal dot cx wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=4099
>
> Rich Felker <bugdal at aerifal dot cx> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |bugdal at aerifal dot cx
>
> --- Comment #2 from Rich Felker <bugdal at aerifal dot cx> ---
> mmap is not the solution; mmap-by-default is not an option because it will
> SIGBUS under circumstances you cannot control. The solution is just decoupling
> cache size from st_blksize, either never using st_blksize at all (and avoiding
> the expensive fstat syscall at open time if possible) or only using it when
> it's less than a reasonable upper bound like 8-64k.
>
For reading my comment was relevant unless you could find how produce
SIGBUS for fopen(foo,"rm").
Writing is different issue, a good upper bound looks ok (But I would
prefer to flush once per 100ms or so.)
--
You are receiving this mail because:
You are on the CC list for the bug.