public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Bence Szépkúti" <szepkuti.bence@gmail.com>
To: cygwin@cygwin.com
Subject: vfork() question
Date: Sat, 27 Jul 2019 10:02:00 -0000	[thread overview]
Message-ID: <CAMkWRsnq5etg984NswsqVXi5T3earBPtgU-gO4zKwknn_HfrTQ@mail.gmail.com> (raw)

Hello,

I was poking around in the fork() code in Cygwin, and was wondering if
someone could explain to me / point me to a discussion of why the NEWVFORK
code was abandoned.

I realise that this code had been disabled as "not working" since 2008,
however I am interested in why this was the case. Was the concept behind
"short-circuiting" vfork itself unfeasible in the context of Cygwin? Was a
compatible implementation too complex / too slow to be worth it compared to
a regular fork?

Any insight is appreciated.

Thanks,
Bence

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2019-07-27 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 10:02 Bence Szépkúti [this message]
2019-07-27 10:50 ` Andrey Repin
2019-07-29  7:57 ` 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=CAMkWRsnq5etg984NswsqVXi5T3earBPtgU-gO4zKwknn_HfrTQ@mail.gmail.com \
    --to=szepkuti.bence@gmail.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).