From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
To: Dan Aloni <da-x@gmx.net>
Cc: dank@kegel.com, linux-kernel@vger.kernel.org, brunner@nic-naa.net
Subject: Re: 32-bit process ids (was: Re: idea to enhance get_pid())
Date: Sat, 20 Apr 2002 16:00:07 -0400 [thread overview]
Message-ID: <200204202000.g3KK07s07372@nic-naa.net> (raw)
In-Reply-To: Your message of "20 Apr 2002 22:12:14 +0300." <1019329937.24728.111.camel@callisto.yi.org>
> According to the kernel patch made by the people at Cluster
> Infrastructure ( http://ci-linux.sourceforge.net/ ), today
> it is clear that the upper 16 bits of the pid are used for the node
> number.
This is the one thing I let through back in 1984. Nixdorff wanted to use
parts of the processID for processorID. Now I don't have my authors' copy
of XPG/1 CAE anymore, but I still have a lasting sense of chagrin that as
trivially exhausted resource as a pid had bits shaved off for mid-80s SMP
machines. Granted, our pid_t of the time was 16 bits, and an Intel HyperCube
made a big dent in the remaining bits-for-pid'ing, and current pid_t's on
32-bit boxen is is 32 bits, and MPP boxes are few and far between -- but
really large clusters are possible.
$.02
Eric
prev parent reply other threads:[~2002-04-20 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 17:50 idea to enhance get_pid() Dan Kegel
2002-04-20 19:12 ` 32-bit process ids (was: Re: idea to enhance get_pid()) Dan Aloni
2002-04-20 20:00 ` Eric Brunner-Williams in Portland Maine [this message]
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=200204202000.g3KK07s07372@nic-naa.net \
--to=brunner@nic-naa.net \
--cc=da-x@gmx.net \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®