public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Limit for number of child processes
Date: Wed, 26 Aug 2020 19:57:24 +0200	[thread overview]
Message-ID: <20200826175724.GQ3272@calimero.vinschen.de> (raw)
In-Reply-To: <000401d67ba0$8b1f33b0$a15d9b10$@gmail.com>

On Aug 26 14:00, Kristian Ivarsson via Cygwin wrote:
> Dear cygwin folks
> 
> It seems like there's a limit of the number of possible child processes
> defined to 256 with 'NPROCS' in //winsup/cygwin/child_info.h used in
> 'cprocs' in //winsup/cygwin/sigproc.cc
> 
> 256 is quite few possible children in an enterprise environment and perhaps
> the limit should be limited by the physical resources or possibly Windows ?

The info has to be kept available in the process itself so we need
this array of NPROCS * sizeof (pinfo).

Of course, there's no reason to use a static array, the code could just
as well use a dynamically allocated array or a linked list.  It's just
not the way it is right now and would need a patch or rewrite.

As for the static array, sizeof pinfo is 64, so the current size of
the array is just 16K.  We could easily bump it to 64K with NPROCS
raised to 1024 for the next Cygwin release, at least on 64 bit.
I don't think we should raise this limit for 32 bit Cygwin, which is
kind of EOL anyway, given the massive restrictions.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

  reply	other threads:[~2020-08-26 17:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 12:00 sten.kristian.ivarsson
2020-08-26 17:57 ` Corinna Vinschen [this message]
2020-08-27 12:17   ` Sv: " sten.kristian.ivarsson
2020-08-28  1:42     ` Ken Brown
2020-08-28  8:35       ` Corinna Vinschen
2020-08-28  8:38       ` Sv: " sten.kristian.ivarsson
2020-08-28 12:29         ` Ken Brown
2020-08-28 13:36           ` Corinna Vinschen
2020-08-28 14:09             ` Sv: " sten.kristian.ivarsson
2020-08-28 16:02             ` Ken Brown
2020-08-28 17:39               ` Corinna Vinschen
2020-08-29 10:01                 ` 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=20200826175724.GQ3272@calimero.vinschen.de \
    --to=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).