public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Chris January" <chris@atomice.net>, <cygwin@cygwin.com>
Subject: RE: Copy-on-write fork
Date: Fri, 19 Apr 2002 20:26:00 -0000	[thread overview]
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5E92@itdomain003.itdomain.net.au> (raw)



> -----Original Message-----
> From: Chris January [mailto:chris@atomice.net] 
> Sent: Saturday, April 20, 2002 12:07 PM
> To: cygwin@cygwin.com
> Subject: Copy-on-write fork
> 
> 
> This is mainly a question aimed at Christopher Faylor, but 
> maybe someone else knows the answer. My question is, with 
> regard to Chris's post "Re: copy-on-write (oh well)" 
> [http://www.cygwin.com/ml/cygwin-developers/2000-07/msg00026.h
> tml], does anyone know why a copy-on-write implementation of 
> fork takes longer than the current Cygwin version?? 

What would be interesting would be to closely monitor the relevant
perfmon items and see if you can determine the thing causing the delay.
You'd probably need a custom program to get enough detail though :[.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-04-20  3:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19 20:26 Robert Collins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20  8:01 Chris January
2002-04-19 19:18 Chris January
2002-04-19 19:29 ` Christopher Faylor
2002-04-19 19:58   ` Gary R. Van Sickle
2002-10-21 15:58 ` Sven Köhler
2002-10-21 16:50   ` Chris January
2002-10-21 21:41     ` Gary R. Van Sickle
2002-10-22 12:25     ` Sven Köhler

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=FC169E059D1A0442A04C40F86D9BA7600C5E92@itdomain003.itdomain.net.au \
    --to=robert.collins@itdomain.com.au \
    --cc=chris@atomice.net \
    --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).