public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Peter Dons Tychsen <donpedro@tdcadsl.dk>
To: cygwin@cygwin.com
Subject: Re: Synchronization problem with posix_spawn
Date: Thu, 20 Aug 2020 07:40:37 +0200	[thread overview]
Message-ID: <1ae8de15bb74efb7207299d2dba92cdef88d9a94.camel@tdcadsl.dk> (raw)
In-Reply-To: <20200803105004.GK460314@calimero.vinschen.de>

Hi Corinna,

> spawn alone doesn't cut it, due to the requirement to support the
> additional file actions and spawn atributes POSIX defines.  This
> would require a revamp of Cygwin's spawn functionality, which is
> already quite complicated.  So this is something I'm only willing
> to do in homeopathic doses.

OK. I can see that most of the processing of the options are done
seperately. We could to start with create a shortcut that calls
spawn[vpe]() instead if there are no options specified? That would
speed up most cases. Then we could add the extra cases later if needed.

Would that be an acceptable patch? 

The reason i am pushing for this is that allot of developers i interact
with get the feeling cygwin is slow. When i look into their cases it is
almost always because they use programs that end up calling fork()
allot (large shell scripts, makefiles, etc.). Almost all modern
versions of these programs have support for calling posix_spawn()
instead when creating processes, which would (if we changed it) speed
up these cases dramatically if it avoided fork(). It would simply make
cygwin more appealing to this group of users.

Thanks,

/pedro

  reply	other threads:[~2020-08-20  5:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 20:17 Ken Brown
2020-07-29 23:12 ` Ken Brown
2020-07-30 11:59   ` Corinna Vinschen
2020-07-30 17:17     ` Corinna Vinschen
2020-07-30 23:04       ` Ken Brown
2020-07-31  8:10         ` Corinna Vinschen
2020-08-03  9:10           ` Peter Dons Tychsen
2020-08-03 10:50             ` Corinna Vinschen
2020-08-20  5:40               ` Peter Dons Tychsen [this message]
2020-08-20 12:50                 ` Corinna Vinschen
2020-08-21  7:58                   ` Peter Dons Tychsen

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=1ae8de15bb74efb7207299d2dba92cdef88d9a94.camel@tdcadsl.dk \
    --to=donpedro@tdcadsl.dk \
    --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).