* bdflush way too agressive
@ 2000-11-21 13:14 Anton Blanchard
0 siblings, 0 replies; only message in thread
From: Anton Blanchard @ 2000-11-21 13:14 UTC (permalink / raw)
To: linux-kernel
Hi,
The current defaults for bdflush make it start async flushing when 20% of
buffers are dirty and sync flush when 40% of buffers are dirty. I think
these defaults are way off but apparently it is intentional. (sync flushing
should be a last ditch effort when free memory is getting low and 40%
on our 2G RAM test machine is not low!).
Regardless of my opinions there remains the problem that I cannot set sane
values for these options since one is hardcoded as 2 times the other. We
should have another bdflush sysctl variable so it can be tuned (eg in
my case 90%/95%).
Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-11-21 13:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-11-21 13:14 bdflush way too agressive Anton Blanchard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox