From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762236AbXHFDZ1 (ORCPT ); Sun, 5 Aug 2007 23:25:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757832AbXHFDZN (ORCPT ); Sun, 5 Aug 2007 23:25:13 -0400 Received: from [212.12.190.118] ([212.12.190.118]:33426 "EHLO raad.intranet" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1753351AbXHFDZM (ORCPT ); Sun, 5 Aug 2007 23:25:12 -0400 From: Al Boldi To: linux-fsdevel@vger.kernel.org Subject: [RFC] VFS: mnotify (was: [PATCH 00/23] per device dirty throttling -v8) Date: Mon, 6 Aug 2007 06:25:20 +0300 User-Agent: KMail/1.5 Cc: linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200708060625.20917.a1426z@gawab.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jakob Oestergaard wrote: > Why on earth would you cripple the kernel defaults for ext3 (which is a > fine FS for boot/root filesystems), when the *fundamental* problem you > really want to solve lie much deeper in the implementation of the > filesystem? Noatime doesn't solve the problem, it just makes it "less > horrible". inotify could easily solve the atime problem, but it's got the drawback of forcing the user to register each and every file/dir of interest, which isn't really reasonable on TB-filesystems. It could be feasible to introduce mnotify, which would notify the user of meta changes, like atime, across the filesystem. Something like mnotify could also be helpful in CoW situations, provided it supported an in-sync interface. Thanks! -- Al