[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070804165604.GA2310@elte.hu>
Date: Sat, 4 Aug 2007 18:56:04 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, miklos@...redi.hu, 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
Subject: Re: [PATCH 00/23] per device dirty throttling -v8
* Andrew Morton <akpm@...ux-foundation.org> wrote:
> > yeah, it's really ugly. But otherwise i've got no real complaint
> > about ext3 - with the obligatory qualification that
> > "noatime,nodiratime" in /etc/fstab is a must. This speeds up things
> > very visibly - especially when lots of files are accessed. It's kind
> > of weird that every Linux desktop and server is hurt by a noticeable
> > IO performance slowdown due to the constant atime updates,
>
> Not just more IO: it will cause great gobs of blockdev pagecache to
> remain in memory, too.
i tried to convince distro folks about it ... but there's fear,
uncertainty and doubt about touching /etc/fstab and i suspect no major
distro will do it until another does it - which is a catch-22 :-/ So i
guess we should add a kernel config option that allows the kernel rpm
maker to just disable atime by default. (re-enableable via boot-line and
fstab entry too) [That new kernel config option would be disabled by
default.] That makes it much easier to control and introduce.
Ingo
-
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