[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070804171724.GA4740@elte.hu>
Date: Sat, 4 Aug 2007 19:17:24 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Diego Calleja <diegocg@...il.com>
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,
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
Subject: Re: [PATCH 00/23] per device dirty throttling -v8
* Diego Calleja <diegocg@...il.com> wrote:
> El Sat, 4 Aug 2007 18:37:33 +0200, Ingo Molnar <mingo@...e.hu> escribió:
>
> > thousands of applications. So for most file workloads we give
> > Windows a 20%-30% performance edge, for almost nothing. (for
> > RAM-starved kernel builds the performance difference between atime
> > and noatime+nodiratime setups is more on the order of 40%)
>
> Just curious - do you have numbers with relatime?
nope. Stupid question, i just tried it and got this:
EXT3-fs: Unrecognized mount option "relatime" or missing value
i've got util-linux-2.13-0.46.fc6 and 2.6.22 on that box, shouldnt that
be recent enough? As far as i can see it from the kernel-side code, this
works on the general VFS level and hence should be supported by ext3
already.
even relatime means one extra write IO after a file has been created,
but at least for read-mostly files it avoids the continuous atime
update.
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