Re: [PATCH 00/23] per device dirty throttling -v8

On Sun, Aug 05, 2007 at 02:26:53AM +0200, Andi Kleen wrote:
> I always thought the right solution would be to just sync atime only
> very very lazily. This means if a inode is only dirty because of an
> atime update put it on a "only write out when there is nothing to do
> or the memory is really needed" list.

Which is the policy I implemented for XFS a while ago.

-
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: [PATCH 00/23] per device dirty throttling -v8
  - From: Andi Kleen <[email protected]>

References:
- [PATCH 00/23] per device dirty throttling -v8
  - From: Peter Zijlstra <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Linus Torvalds <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Linus Torvalds <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Ingo Molnar <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v8
  - From: Andi Kleen <[email protected]>

Prev by Date: Re: [PATCH 4/5] UML - Simplify helper stack handling
Next by Date: Re: [PATCH/RFT] finish i386 and x86-64 sysdata conversion
Previous by thread: Re: [PATCH 00/23] per device dirty throttling -v8
Next by thread: Re: [PATCH 00/23] per device dirty throttling -v8
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]