public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: python select() is limited to fds < 64
Date: Wed, 23 Mar 2011 15:02:00 -0000	[thread overview]
Message-ID: <20110323150038.GE13862@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4D89DA22.9010404@dronecode.org.uk>

On Wed, Mar 23, 2011 at 11:31:46AM +0000, Jon TURNEY wrote:
>On 22/03/2011 20:08, Christopher Faylor wrote:
>>On Tue, Mar 22, 2011 at 08:53:34PM +0100, V??clav Haisman wrote:
>>>Jon TURNEY wrote, On 22.3.2011 20:29:
>>>>
>>>>python seems to be built with the default value of FD_SETSIZE, which is
>>>>only 64 on cygwin.
>>>Is this not because of the inherent limitation of
>>>WaitForMultipleObjects() call?
>>
>>Yep.  Without a rewrite, it's a hard limit to Cygwin's select().
>
>Please read my email more closely.  I am not saying "python select() is
>limited to waiting on 64 fds or less", I am saying "python select() is
>limited to waiting on fd which are less than 64"

I forgot to add one bit of data.  Unless you go out of your way to
change it, Cygwin's select can't wait for an fd > 63.  It's basically a
bit mask.  So, there are two limitations: 1) the number of handles that
you can wait for with WaitForMultipleObjects() and 2) the size of
Cygwin's fd_set.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-03-23 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 19:50 Jon TURNEY
2011-03-22 20:59 ` Václav Haisman
2011-03-22 23:45   ` Christopher Faylor
2011-03-23 12:09     ` Jon TURNEY
2011-03-23 15:02       ` Christopher Faylor [this message]
2011-03-23 15:24         ` Eric Blake
2011-03-23 16:50         ` Jon TURNEY
2011-03-23 20:28           ` Christopher Faylor
2011-03-24 16:11             ` Jon TURNEY
2011-04-21  1:07 Bert Belder

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=20110323150038.GE13862@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).