From: Matt Johnston <mlkm@caifex.org>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: random PID generation
Date: Fri, 23 Feb 2001 23:40:37 +0800 [thread overview]
Message-ID: <01022323403700.00325@box.caifex.org> (raw)
In-Reply-To: <27525795B28BD311B28D00500481B7601F0F02@ftrs1.intranet.ftr.nl>
In-Reply-To: <27525795B28BD311B28D00500481B7601F0F02@ftrs1.intranet.ftr.nl>
OpenBSD has a working implementation, might be worth looking at???
Cheers,
Matt Johnston.
On Fri, 23 Feb 2001 23:34, Heusden, Folkert van wrote:
> >> My code runs trough the whole task_list to see if a chosen pid is
> >> already
> >>
> >> in use or not.
> >
> > But it doesn't check for a recently used PID. Lets say your system is
> > exhausting 1000 PIDs/second, and that there is a window of 20ms between
>
> you
>
> > determining which PID to send to, and the recipient process receiving it.
>
> Ah, I get your point. Good point :o)
>
> I was thinking: I could split the PIDs up in 2...16383 and 16384-32767 and
> then
> switch between them when a process ends? nah, that doesn't help it.
> hmmm.
> I think random increments (instead of last_pid+1) would be the best thing
> to do then?
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-23 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 15:34 random PID generation Heusden, Folkert van
2001-02-23 15:40 ` Matt Johnston [this message]
2001-02-23 17:14 ` Sean Hunter
2001-02-23 17:50 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 10:35 Heusden, Folkert van
2001-02-23 13:20 Heusden, Folkert van
2001-02-23 14:18 ` bert hubert
2001-02-22 15:35 Heusden, Folkert van
2001-02-22 22:24 ` bert hubert
2001-02-22 21:42 ` H. Peter Anvin
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=01022323403700.00325@box.caifex.org \
--to=mlkm@caifex.org \
--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;
as well as URLs for NNTP newsgroup(s).