Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760293AbXHENq4 (ORCPT ); Sun, 5 Aug 2007 09:46:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751427AbXHENqr (ORCPT ); Sun, 5 Aug 2007 09:46:47 -0400 Received: from unthought.net ([212.97.129.88]:4745 "EHLO unthought.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751371AbXHENqq (ORCPT ); Sun, 5 Aug 2007 09:46:46 -0400 Date: Sun, 5 Aug 2007 15:46:45 +0200 From: Jakob Oestergaard To: Ingo Molnar Cc: Jeff Garzik , Linus Torvalds , miklos@szeredi.hu, akpm@linux-foundation.org, neilb@suse.de, dgc@sgi.com, tomoki.sekiyama.qu@hitachi.com, Peter Zijlstra , linux-mm@kvack.org, Linux Kernel Mailing List , nikita@clusterfs.com, trond.myklebust@fys.uio.no, yingchao.zhou@gmail.com, richard@rsk.demon.co.uk, david@lang.hm Subject: Re: [PATCH 00/23] per device dirty throttling -v8 Message-ID: <20070805134645.GD4246@unthought.net> Mail-Followup-To: Jakob Oestergaard , Ingo Molnar , Jeff Garzik , Linus Torvalds , miklos@szeredi.hu, akpm@linux-foundation.org, neilb@suse.de, dgc@sgi.com, tomoki.sekiyama.qu@hitachi.com, Peter Zijlstra , linux-mm@kvack.org, Linux Kernel Mailing List , nikita@clusterfs.com, trond.myklebust@fys.uio.no, yingchao.zhou@gmail.com, richard@rsk.demon.co.uk, david@lang.hm References: <20070804070737.GA940@elte.hu> <20070804103347.GA1956@elte.hu> <20070804163733.GA31001@elte.hu> <46B4C0A8.1000902@garzik.org> <20070805102021.GA4246@unthought.net> <46B5A996.5060006@garzik.org> <20070805105850.GC4246@unthought.net> <20070805124648.GA21173@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070805124648.GA21173@elte.hu> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1651 Lines: 48 On Sun, Aug 05, 2007 at 02:46:48PM +0200, Ingo Molnar wrote: > > * Jakob Oestergaard wrote: > > > > If you can show massive amounts of users that will actually be > > > negatively impacted, please present hard evidence. > > > > > > Otherwise all this is useless hot air. > > > > Peace Jeff :) > > > > In another mail, I gave an example with tmpreaper clearing out unused > > files; if some of those files are only read and never modified, > > tmpreaper would start deleting files which were still frequently used. > > > > That's a regression, the way I see it. As for 'massive amounts of > > users', well, tmpreaper exists in most distros, so it's possible it > > has other users than just me. > > you mean tmpwatch? Same same. > The trivial change below fixes this. And with that > we've come to the end of an extremely short list of atime dependencies. Please read what I wrote, not what you think I wrote. If I only *read* those files, the mtime will not be updated, only the atime. And the files *will* then magically begin to disappear although they are frequently used. That will happen with a standard piece of software in a standard configuration, in a scenario that may or may not be common... I have no idea how common such a setup is - but I know how much it would suck to have files magically disappearing because of a kernel upgrade :) -- / jakob - 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/