From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: getdtablesize: always return OPEN_MAX_MAX
Date: Mon, 1 Feb 2021 11:46:15 +0100 [thread overview]
Message-ID: <20210201104615.GL375565@calimero.vinschen.de> (raw)
In-Reply-To: <20210201095054.GF375565@calimero.vinschen.de>
On Feb 1 10:50, Corinna Vinschen via Cygwin-patches wrote:
> On Jan 28 15:33, Ken Brown via Cygwin-patches wrote:
> > On 1/28/2021 11:07 AM, Corinna Vinschen via Cygwin-patches wrote:
> > > One problem is that there are some applications in the wild which run
> > > loops up to either sysconf(_SC_OPEN_MAX) or OPEN_MAX to handle open
> > > descriptors. tcsh is one of them. It may slow done tcsh quite a bit
> > > if the loop runs to 3200 now every time.
> >
> > I don't use tcsh. Is it easy to test this?
>
> I just checked the source. In the olden days, before the invention of
> close-on-exec, tcsh closed all descriptors > 2 up to OPEN_MAX prior to
> starting any executable.
>
> With close-on-exec this happens only at startup and after an error
> occured.
>
> So testing should be easy: The tcsh startup may be noticably slower.
I checked this right now and I don't see a noticable, i. .e, any,
difference.
Corinna
prev parent reply other threads:[~2021-02-01 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 2:51 Ken Brown
2021-01-28 10:20 ` Corinna Vinschen
2021-01-28 13:42 ` Ken Brown
2021-01-28 16:07 ` Corinna Vinschen
2021-01-28 16:13 ` Corinna Vinschen
2021-01-28 22:28 ` Ken Brown
2021-01-29 19:23 ` Ken Brown
2021-02-01 9:42 ` Corinna Vinschen
2021-01-28 20:33 ` Ken Brown
2021-02-01 9:50 ` Corinna Vinschen
2021-02-01 10:46 ` Corinna Vinschen [this message]
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=20210201104615.GL375565@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).