Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 27 Aug 2002 13:27:03 +0400
From: egor duda <deo AT logos-m DOT ru>
Reply-To: egor duda <cygwin AT cygwin DOT com>
Organization: deo
Message-ID: <777081412.20020827132703@logos-m.ru>
To: Corinna Vinschen <cygwin AT cygwin DOT com>
Subject: Re: poll function in cygwin
In-Reply-To: <20020827111431.T5475@cygbert.vinschen.de>
References: <A220D2C5610C714BA00110F541A4ABD9012644CE AT home DOT fsoft DOT fpt DOT vn>
 <20020827111431 DOT T5475 AT cygbert DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Tuesday, 27 August, 2002 Corinna Vinschen corinna-cygwin AT cygwin DOT com wrote:

CV> On Tue, Aug 27, 2002 at 02:33:40PM +0700, Nguyen Minh Sang wrote:
>>    On cygwin, function:
>> int poll(struct pollfd *ufds, unsigned int nfds, int timeout);
>> 
>> The maximum of nfds = ?

CV> Theoretically there is no maximum.  In practice the maximum is a
CV> function of the memory available.

I was thinking that maximum number of handles which can be waited via
WaitForMultipleObjects() is 64, thus limiting a number of handles that
can be select()ed. It's probably possible to work around such
limitation in cygwin select() but either i've missed something or no
such workaround was created in cygwin code. 

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/