From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: [PATCH 0/4] getdtablesize, OPEN_MAX, etc.
Date: Fri, 29 Jan 2021 14:24:17 -0500 [thread overview]
Message-ID: <20210129192421.1651-1-kbrown@cornell.edu> (raw)
This patchset is an extension of the patch submitted here:
https://cygwin.com/pipermail/cygwin-patches/2021q1/011060.html
That patch is included as the first patch in this set. The change to
OPEN_MAX still needs testing to see if it has too much impact on the
performance of tcsh.
I've make a first attempt to implement the suggestion of adding a new
<cygwin/limits.h> header. At this writing I'm not completely sure
that I fully understand the purpose of that. My choice of which
macros to define in it might need to be changed.
Ken Brown (4):
Cygwin: getdtablesize: always return OPEN_MAX_MAX
Cygwin: sysconf, getrlimit: don't call getdtablesize
Cygwin: remove the OPEN_MAX_MAX macro
Cygwin: include/cygwin/limits.h: new header
winsup/cygwin/dtable.cc | 8 +--
winsup/cygwin/dtable.h | 2 -
winsup/cygwin/fcntl.cc | 2 +-
winsup/cygwin/include/cygwin/limits.h | 65 ++++++++++++++++++++
winsup/cygwin/include/limits.h | 85 +++++++++++----------------
winsup/cygwin/resource.cc | 5 +-
winsup/cygwin/syscalls.cc | 8 +--
winsup/cygwin/sysconf.cc | 11 +---
8 files changed, 111 insertions(+), 75 deletions(-)
create mode 100644 winsup/cygwin/include/cygwin/limits.h
--
2.30.0
next reply other threads:[~2021-01-29 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:24 Ken Brown [this message]
2021-01-29 19:24 ` [PATCH 1/4] Cygwin: getdtablesize: always return OPEN_MAX_MAX Ken Brown
2021-01-29 19:24 ` [PATCH 2/4] Cygwin: sysconf, getrlimit: don't call getdtablesize Ken Brown
2021-01-29 19:24 ` [PATCH 3/4] Cygwin: remove the OPEN_MAX_MAX macro Ken Brown
2021-01-29 19:24 ` [PATCH 4/4] Cygwin: include/cygwin/limits.h: new header Ken Brown
2021-02-01 10:46 ` [PATCH 0/4] getdtablesize, OPEN_MAX, etc Corinna Vinschen
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=20210129192421.1651-1-kbrown@cornell.edu \
--to=kbrown@cornell.edu \
--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).