From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265250AbUGSNdu (ORCPT ); Mon, 19 Jul 2004 09:33:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265253AbUGSNdu (ORCPT ); Mon, 19 Jul 2004 09:33:50 -0400 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]:31943 "EHLO zcars04f.nortelnetworks.com") by vger.kernel.org with ESMTP id S265250AbUGSNdt (ORCPT ); Mon, 19 Jul 2004 09:33:49 -0400 Message-ID: <40FBCD8F.1080300@nortelnetworks.com> Date: Mon, 19 Jul 2004 09:33:03 -0400 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Chris Friesen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Kent CC: John McCutchan , Davide Libenzi , Linux Kernel Mailing List , nautilus-list@gnome.org Subject: Re: [PATCH] inotify 0.5 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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. Chris