From: Stephan Menzel <stephan42@chinguarime.net>
To: linux-kernel@vger.kernel.org
Subject: [FS] New monitor framework in 2.6.10?
Date: Mon, 15 Nov 2004 11:13:06 +0100 [thread overview]
Message-ID: <200411151113.06386.stephan42@chinguarime.net> (raw)
Hi,
i'm maintaining a kernel patch which is monitoring file system activity
underneath a special directory tree and reporting occuring events via a
character device to userland where it is processed.
Right now, this patch works via a number of hooks in fs/read-write.c and
fs/namei.c.
This is not really efficient at the moment because this way I get an event for
any written block and not per file which can slow things down a lot.
A couple of days ago I heard rumours about a new feature in 2.6.10 which will
be exactly for this kind of purpose. Some kind of monitor frameworks that can
generate events for all sorts of things. Sorry, I don't know any more about
it.
Is that true?
Would that be suitable for my task?
And where can I get information about it?
Greetings...
Stephan
next reply other threads:[~2004-11-15 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 10:13 Stephan Menzel [this message]
2004-11-15 10:23 ` Jan Engelhardt
2004-11-15 10:42 ` Stephan Menzel
2004-11-15 12:44 ` Stephan Menzel
2004-11-15 13:29 ` Paolo Ciarrocchi
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=200411151113.06386.stephan42@chinguarime.net \
--to=stephan42@chinguarime.net \
--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®