Re: Change in default vm_dirty_ratio
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Jun 2007 10:17:40 -0700 (PDT)
On Wed, 20 Jun 2007, Peter Zijlstra wrote:
Building on the per BDI patches, how about integrating feedback from the
full-ness of device queues. That is, when we are happily doing IO and we
cannot possibly saturate the active devices (as measured by their queue
never reaching 75%?) then we can safely increase the total dirty limit.
The really annoying things are the one-off things. You've been happily
working for a while (never even being _close_ to saturatign any IO
queues), and then you untar a large tree.
If the kernel now let's you dirty lots of memory, you'll have a very
unpleasant experience.
And with hot-pluggable devices (which is where most of the throughput
problems tend to be!), the "one-off" thing is not a "just after reboot"
kind of situation.
So you'd have to be pretty smart about it.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Change in default vm_dirty_ratio
- From: Arjan van de Ven
- Re: Change in default vm_dirty_ratio
- References:
- Change in default vm_dirty_ratio
- From: Tim Chen
- Re: Change in default vm_dirty_ratio
- From: Andrew Morton
- Re: Change in default vm_dirty_ratio
- From: Dave Jones
- Re: Change in default vm_dirty_ratio
- From: Andrew Morton
- Re: Change in default vm_dirty_ratio
- From: Peter Zijlstra
- Change in default vm_dirty_ratio
- Prev by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Next by Date: Re: [RFC] clocksouce implementation for powerpc
- Previous by thread: Re: Change in default vm_dirty_ratio
- Next by thread: Re: Change in default vm_dirty_ratio
- Index(es):