From: Jon Turney <jon.turney@dronecode.org.uk>
To: Corinna Vinschen <corinna-cygwin@cygwin.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Typo in <sys/select.h>?
Date: Wed, 6 Jul 2022 15:01:23 +0100 [thread overview]
Message-ID: <ea3de3f0-ed55-bfcf-f543-a95e38b98599@dronecode.org.uk> (raw)
In-Reply-To: <YsU9APd87h5vUJtZ@calimero.vinschen.de>
On 06/07/2022 08:42, Corinna Vinschen wrote:
> On Jul 5 17:51, Ken Brown wrote:
>> On 7/5/2022 10:13 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>
> I guess we can change FD_SETSIZE to 1024 as on Linux, albeit this has no
> real meaning on Cygwin. On Linux, select(2) is really only capable to
> handle file descriptors numbers up to descriptor number 1023, but Cygwin
> doesn't have this problem. FD_SETSIZE == 64 was only something to save
> space. The bigger FD_SETSIZE, the bigger are the default fd_sets,
> something you don't want on small targets.
>
> So, yeah, something like
>
> #ifndef FD_SETSIZE
> # ifdef __CYGWIN__
> # define FD_SETSIZE 1024
> # else
> # define FD_SETSIZE 64
> # endif
> #endif
Remember that 64 is MAXIMUM_WAIT_OBJECTS for WaitForMultipleObjects(),
the underlying Win32 API used to implement select(), so using more than
64 hits some complex code to work around that...
next prev parent reply other threads:[~2022-07-06 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 14:13 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-05 14:55 ` Andrey Repin
2022-07-05 21:51 ` Ken Brown
2022-07-06 7:42 ` Corinna Vinschen
2022-07-06 14:01 ` Jon Turney [this message]
2022-07-06 14:15 ` Corinna Vinschen
2022-07-06 14:22 ` Corinna Vinschen
2022-07-05 15:11 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-06 13:19 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-06 14:17 ` Corinna Vinschen
2022-07-06 14:17 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-06 14:26 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-06 15:07 ` Corinna Vinschen
2022-07-06 15:57 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-06 17:03 ` Ken Brown
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=ea3de3f0-ed55-bfcf-f543-a95e38b98599@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=corinna-cygwin@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).