From: Amy Griffis <amy.griffis@hp.com>
To: linux-kernel@vger.kernel.org
Cc: John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] inotify: split kernel API from userspace support
Date: Fri, 2 Jun 2006 08:32:34 -0400 [thread overview]
Message-ID: <20060602123234.GA6586@zk3.dec.com> (raw)
In-Reply-To: <20060601150702.GA2171@zk3.dec.com>
Here is a more descriptive changelog message for this patch:
This patch introduces a kernel API for inotify, making it possible for
kernel modules to benefit from inotify's mechanism for watching
inodes.
To provide the kernel API, the current inotify code is split into two
parts: core functionality remains in inotify.c, and functionality
supporting userspace is moved to a new file inotify_user.c. The
inotify_device struct is split into inotify_handle (idr, watch list,
inotify operations) and inotify_device (event queue for userspace).
This patch also makes struct inotify_watch public so it can be
embedded in a caller's own watch structure.
In order to separate the find/update watch and add watch operations
for the kernel API, this patch adds a second per-inotify_device mutex
to prevent a userspace caller from adding the same watch twice.
This patch retains the original assumption that there will be more
watches per inotify_handle than watches on any given inode, and
performs the search for existing watches accordingly.
On Thu, Jun 01, 2006 at 11:07:02AM -0400, Amy Griffis wrote:
> Signed-off-by: Amy Griffis <amy.griffis@hp.com>
>
> ---
>
> fs/Kconfig | 24 +
> fs/Makefile | 1
> fs/inotify.c | 941 +++++++++++------------------------------------
> fs/inotify_user.c | 717 ++++++++++++++++++++++++++++++++++++
> include/linux/inotify.h | 76 ++++
> include/linux/sched.h | 2
> kernel/sysctl.c | 4
> kernel/user.c | 2
> 8 files changed, 1046 insertions(+), 721 deletions(-)
> create mode 100644 fs/inotify_user.c
next prev parent reply other threads:[~2006-06-02 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 15:07 [PATCH] inotify: split kernel API from userspace support Amy Griffis
2006-06-01 15:08 ` [PATCH 2/5] inotify: add name's inode to event handler Amy Griffis
2006-06-01 15:10 ` [PATCH 3/5] inotify: add interfaces to kernel API Amy Griffis
2006-06-01 15:10 ` [PATCH 4/5] inotify: allow watch removal from event handler Amy Griffis
2006-06-01 15:11 ` [PATCH 5/5] inotify: update kernel documentation Amy Griffis
2006-06-01 17:46 ` [PATCH] inotify: split kernel API from userspace support Robert Love
[not found] ` <1149216713.2865.0.camel@localhost.localdomain>
2006-06-02 2:51 ` John McCutchan
2006-06-02 12:32 ` Amy Griffis [this message]
2006-06-06 21:06 ` Pavel Machek
2006-06-08 3:59 ` Amy Griffis
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=20060602123234.GA6586@zk3.dec.com \
--to=amy.griffis@hp.com \
--cc=akpm@osdl.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.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