delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/07/19/09:59:21

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Lotus-FromDomain: JPMORGAN AT SMTP
From: "Noel L Yap" <yap_noel AT jpmorgan DOT com>
To: mark AT npsl DOT co DOT uk
cc: Cygwin AT sources DOT redhat DOT com
Message-ID: <85256921.004C60EA.00@nyc-ntgw-n01.ny.jpmorgan.com>
Date: Wed, 19 Jul 2000 09:54:19 -0400
Subject: RE: Extending cygwin's process table
Mime-Version: 1.0

"Monotonic" means that a sequence moves in the same direction (or stays the
same).  It doesn't mean that it's sequential.  So, for example, the sequence
"100, 101, 103" is monotonic.

The reason pids are non-monotonic is 'cos they cycle.  Pids aren't unique
through time -- they're reused.

Noel




mark AT npsl DOT co DOT uk on 2000.07.19 09:17:35

To:   yap_noel AT jpmorgan DOT com, cygwin AT sources DOT redhat DOT com
cc:
Subject:  RE: Extending cygwin's process table




Isn't pid creation inherently non-monotonic anyway due to multitasking
considerations, i.e.

1.   X w/pid 100 creates Y w/pid 101
2.   A w/pid 2 creates B w/pid 102
3.   Y w/pid 101 creates Z w/pid 103

...so anything that relies on monotonicity just won't be robust.  Just my
2p's worth!

Mark



-----Original Message-----
From: cygwin-owner AT sources DOT redhat DOT com
[mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of Noel L Yap
Sent: Wednesday, July 19, 2000 2:05 PM
To: cygwin AT sources DOT redhat DOT com
Subject: Re: Extending cygwin's process table






cgf AT cygnus DOT com on 2000.07.18 23:43:19
>I'm also toying with trying to more closely tie cygwin pids to windows
>pids.

IMHO, this'd be great.

>Is anyone going to be bothered if pid creation is not monotonic?  By
>that I mean, parent pid 1000 may not create child pid 1001.  It may
>create child pid 27.

I don't think anything should be relying on this behaviour since it's not
always
satisfied (ie when ppid is near the max pid allowed).

>It may still not be feasible to use cygwin pids as windows pids
>(possibly because I don't believe that pid 1 is special to windows) but
>I thought I'd give this a try anyway unless there is something that I'm
>missing.

Yeah, I'm not sure if it's possible, but it's worth a shot (unless someone
out
there knows for sure that it's not possible).

Noel




This communication is for informational purposes only.  It is not intended
as
an offer or solicitation for the purchase or sale of any financial
instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com






This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019