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

Helge Hafting
2007-08-16T10:21:57Z

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.
>
Seems like a good idea. atimes will then be written only by
memory pressure - or umount. The atimes could be wrong after
a crash, but loosing atimes only is not something
I'd worry about.

Helge Hafting