From: Steve French <smfrench@austin.rr.com>
To: Robert Love <rml@novell.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: which ioctls matter across filesystems
Date: Fri, 29 Apr 2005 16:00:44 -0500 [thread overview]
Message-ID: <4272A07C.7000605@austin.rr.com> (raw)
In-Reply-To: <1114807835.6682.156.camel@betsy>
Robert Love wrote:
>So a client adds a watch and the server needs to then physically add the
>inotify watch?
>
>
>
Yes, this creates the interesting situation of two responses (one from
the local client code, and one from the server) potentially coming as a
client changes a file which he has a watch on.
>If you have a user-space, user-space could just add an inotify watch.
>
>But I guess you live entirely in kernel-space? Couldn't we just export
>our "add watch" interface to you?
>
> Robert Love
>
>
>
Yes - add watch could be exported, I don't see a way around this since a
filesystem has to be able to tell the server what to watch. It does not
really matter if that were done in kernel or not, but I would prefer it
to be done in kernel since that would avoid having to ioctl down to the
kernel
next prev parent reply other threads:[~2005-04-29 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 19:22 which ioctls matter across filesystems Steve French
2005-04-29 19:53 ` Trond Myklebust
2005-04-29 20:03 ` Robert Love
2005-04-29 20:42 ` Trond Myklebust
2005-04-29 20:47 ` Robert Love
2005-04-29 21:13 ` Trond Myklebust
2005-04-29 21:22 ` Steve French
2005-04-29 21:38 ` Trond Myklebust
2005-04-29 20:55 ` Steve French
2005-04-29 20:57 ` Robert Love
2005-04-29 21:05 ` Steve French
2005-04-29 20:47 ` Steve French
2005-04-29 20:50 ` Robert Love
2005-04-29 21:00 ` Steve French [this message]
2005-04-29 20:32 ` Steve French
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=4272A07C.7000605@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=trond.myklebust@fys.uio.no \
/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