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: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 28 Nov 2014 16:15:50 +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/>
https://sourceware.org/bugzilla/show_bug.cgi?id=4099
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> ---
For now I think that using custom streams or setvbuf is the only workaround to
this problem.
The immediate solution that springs to mind is to use tunnables to set a
maximum block size that streams will use in the process, and default it to
st_blksize to get the old behaviour by default.
I've added this to the list of tunnables:
https://sourceware.org/glibc/wiki/TuningLibraryRuntimeBehavior
--
You are receiving this mail because:
You are on the CC list for the bug.