All of lore.kernel.org
 help / color / mirror / Atom feed
From: John McCutchan <ttb@tentacle.dhs.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Ian Kent <raven@themaw.net>,
	Davide Libenzi <davidel@xmailserver.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	nautilus-list@gnome.org
Subject: Re: [PATCH] inotify 0.5
Date: Mon, 19 Jul 2004 17:31:30 -0400	[thread overview]
Message-ID: <1090272690.6954.1.camel@vertex> (raw)
In-Reply-To: <40FBCD8F.1080300@nortelnetworks.com>

On Mon, 2004-07-19 at 09:33, Chris Friesen wrote:
> Ian Kent wrote:
> 
> > So the number of watches is restricted to the max number of file
> > handles/process?
> 
> Note: I have not read the code.  We should probably do so before speculating.
> 
> However, it looks like you have one fd, and reading from it gives you a data 
> structure of information about the event.  The max number of watches could be as 
> high as INT_MAX depending on implementation.

Yes you are right. The maximum number of watchers is per-device. I have
it defined as 256 now. Also the maximum number of devices that can be
opened at a time is 8.

John

  reply	other threads:[~2004-07-19 21:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 19:49 [PATCH] inotify 0.5 John McCutchan
2004-07-18 19:53 ` Martin Schlemmer
2004-07-18 20:02   ` John McCutchan
2004-07-18 20:11     ` Martin Schlemmer
2004-07-18 20:22       ` John McCutchan
2004-07-18 23:37 ` Davide Libenzi
2004-07-19  1:42   ` John McCutchan
2004-07-19  8:43     ` Ian Kent
2004-07-19 13:33       ` Chris Friesen
2004-07-19 21:31         ` John McCutchan [this message]
2004-07-20  2:59           ` Eric Lammerts
2004-07-20  3:24             ` John McCutchan
2004-07-20  1:33         ` Ian Kent
2004-07-19  3:37 ` Daniel Veillard

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=1090272690.6954.1.camel@vertex \
    --to=ttb@tentacle.dhs.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nautilus-list@gnome.org \
    --cc=raven@themaw.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.