Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765737AbXHDXci (ORCPT ); Sat, 4 Aug 2007 19:32:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764963AbXHDXc3 (ORCPT ); Sat, 4 Aug 2007 19:32:29 -0400 Received: from ns2.suse.de ([195.135.220.15]:37675 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756226AbXHDXc2 (ORCPT ); Sat, 4 Aug 2007 19:32:28 -0400 To: Ingo Molnar Cc: Linus Torvalds , Peter Zijlstra , linux-mm@kvack.org, linux-kernel@vger.kernel.org, miklos@szeredi.hu, akpm@linux-foundation.org, neilb@suse.de, dgc@sgi.com, tomoki.sekiyama.qu@hitachi.com, nikita@clusterfs.com, trond.myklebust@fys.uio.no, yingchao.zhou@gmail.com, richard@rsk.demon.co.uk Subject: Re: [PATCH 00/23] per device dirty throttling -v8 References: <20070803123712.987126000@chello.nl> <20070804063217.GA25069@elte.hu> <20070804070737.GA940@elte.hu> <20070804103347.GA1956@elte.hu> <20070804163733.GA31001@elte.hu> From: Andi Kleen Date: 05 Aug 2007 02:26:53 +0200 In-Reply-To: <20070804163733.GA31001@elte.hu> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1387 Lines: 21 Ingo Molnar writes: > > 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, while there's just two real users of it: > tmpwatch [which can be configured to use ctime so it's not a big issue] > and some backup tools. (Ok, and mail-notify too i guess.) Out of tens of > 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%) 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. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/