From: Al Boldi <a1426z@gawab.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@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 [thread overview]
Message-ID: <200708060625.20917.a1426z@gawab.com> (raw)
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
reply other threads:[~2007-08-06 3:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200708060625.20917.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®