public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] inotify 0.9
Date: Thu, 16 Sep 2004 10:27:06 -0600	[thread overview]
Message-ID: <4149BEDA.9020307@nortelnetworks.com> (raw)
In-Reply-To: <cic9os$ibd$1@gatekeeper.tmr.com>

Bill Davidsen wrote:

> If I were doing this, and I admit I may not understand all of the 
> features, I would have a bitmap per filesystem of inodes being watched, 
> and anything which did an action which might require notify would check 
> the bit. If the bit were set the filesystem and inode info would be 
> passed to user space which could do anything it wanted.

How do you identify the filesystem?  Whose mount namespace do you use if you 
have multiple processes in different namespaces watching what is really the same 
file?

Chris

  reply	other threads:[~2004-09-16 16:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 15:52 [RFC][PATCH] inotify 0.9 John McCutchan
2004-09-15 18:00 ` Robert Love
2004-09-16 15:07 ` Bill Davidsen
2004-09-16 16:27   ` Chris Friesen [this message]
2004-09-16 22:48     ` Bill Davidsen
2004-09-16 16:39   ` Robert Love
2004-09-20 20:16     ` Bill Davidsen
2004-09-20 21:05       ` Robert Love
2004-09-20 22:59         ` Bill Davidsen
2004-09-21  0:02           ` Robert Love
2004-09-16 16:46   ` Jan Kara
2004-09-16 22:34     ` Bill Davidsen
2004-09-16 22:57       ` David Lang
2004-09-16 23:22       ` Robert Love
2004-09-16 23:35         ` Alan Cox
2004-09-17  2:29           ` Robert Love
2004-09-17  3:08             ` Nicholas Miell
2004-09-17 14:39             ` Alan Cox
2004-09-17 15:48               ` Robert Love
2004-09-17 14:51                 ` Alan Cox
2004-09-17 15:55                   ` Robert Love

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=4149BEDA.9020307@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=davidsen@tmr.com \
    --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