Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)

> One thing to try out (and dammit, I should make it the default now in 
> 2.6.21) is to just make the dirty limits much lower. We've been talking 
> about this for ages, I think this might be the right time to do it.

Could[/should] this stuff be changed from ratios to amounts? Or a quick 
boot-time test to use a ratio if the memory is small and an amount (like 
tax brackets, I would expect) if it's great?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
  - From: Linus Torvalds <[email protected]>

References:
- [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
  - From: Mike Galbraith <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
  - From: Linus Torvalds <[email protected]>

Prev by Date: Re: Linux 2.6.21 - something wrong with dmesg.
Next by Date: Re: [linux-pm] driver power operations (was Re: suspend2 merge)
Previous by thread: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
Next by thread: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]