[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070804192615.GA25600@lazybastard.org>
Date: Sat, 4 Aug 2007 21:26:15 +0200
From: Jörn Engel <joern@...fs.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Jörn Engel <joern@...fs.org>,
Jeff Garzik <jeff@...zik.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
miklos@...redi.hu, akpm@...ux-foundation.org, neilb@...e.de,
dgc@....com, tomoki.sekiyama.qu@...achi.com, nikita@...sterfs.com,
trond.myklebust@....uio.no, yingchao.zhou@...il.com,
richard@....demon.co.uk, david@...g.hm
Subject: Re: [PATCH 00/23] per device dirty throttling -v8
On Sat, 4 August 2007 21:21:30 +0200, Ingo Molnar wrote:
> * Jörn Engel <joern@...fs.org> wrote:
>
> > > I actually vote for that. IMO, distros should turn -on- atime
> > > updates when they know its needed.
> >
> > If you mean "relatime" I concur. "noatime" hurts mutt and others
> > while "relatime" has no known problems, afaics.
>
> so ... one app can keep 30,000+ apps hostage?
>
> i use Mutt myself, on such a filesystem:
>
> /dev/md0 on / type ext3 (rw,noatime,nodiratime,user_xattr)
>
> and i can see no problems, it notices new mails just fine.
Given the choice between only "atime" and "noatime" I'd agree with you.
Heck, I use it myself. But "relatime" seems to combine the best of both
worlds. It currently just suffers from mount not supporting it in any
relevant distro.
Jörn
--
Joern's library part 2:
http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassing-memo.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists