From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932420AbXHFSyS (ORCPT ); Mon, 6 Aug 2007 14:54:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758902AbXHFSyB (ORCPT ); Mon, 6 Aug 2007 14:54:01 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:42498 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758703AbXHFSyA (ORCPT ); Mon, 6 Aug 2007 14:54:00 -0400 Message-ID: <46B76E23.7090102@garzik.org> Date: Mon, 06 Aug 2007 14:53:23 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.12 (X11/20070719) MIME-Version: 1.0 To: Chuck Ebbert CC: Christoph Hellwig , J??rn Engel , Ingo Molnar , Linus Torvalds , Peter Zijlstra , linux-mm@kvack.org, Linux Kernel Mailing List , 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, david@lang.hm Subject: Re: [PATCH 00/23] per device dirty throttling -v8 References: <20070804070737.GA940@elte.hu> <20070804103347.GA1956@elte.hu> <20070804163733.GA31001@elte.hu> <46B4C0A8.1000902@garzik.org> <20070804191205.GA24723@lazybastard.org> <20070804192130.GA25346@elte.hu> <20070804192615.GA25600@lazybastard.org> <20070804194259.GA25753@lazybastard.org> <20070805203602.GB25107@infradead.org> <46B7626C.6050403@redhat.com> In-Reply-To: <46B7626C.6050403@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.9 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Chuck Ebbert wrote: > On 08/05/2007 04:36 PM, Christoph Hellwig wrote: >> Umm, no f**king way. atime selection is 100% policy and belongs into >> userspace. Add to that the problem that we can't actually re-enable >> atimes because of the way the vfs-level mount flags API is designed. >> Instead of doing such a fugly kernel patch just talk to the handfull >> of distributions that matter to update their defaults. > We already tried that here. The response: "If noatime is so great, why > isn't it the default in the kernel?" Yes, and around and around we go :/ Jeff