From: Dan Aloni <da-x@gmx.net>
To: lenny lv <lennylv@hotmail.com>
Cc: linux-kernel@vger.kernel.org, qiang@suda.edu.cn
Subject: Re: idea to enhance get_pid()
Date: 20 Apr 2002 12:59:27 +0300 [thread overview]
Message-ID: <1019296776.24728.40.camel@callisto.yi.org> (raw)
In-Reply-To: <F74PKipeUekcMrvgldU00000fc8@hotmail.com>
On Sat, 2002-04-20 at 12:15, lenny lv wrote:
> I've got an idea to speed up linux/kernel/fork.c/get_pid(). Why not use
> bitmap to alloc/free the pids? Is it because 4KB(32K/8) memory scanning is
> slower than the current get_pid() version? Does anyone benchmark them?
This could have been a good idea if Linux was to stay with 15-bit pids
forever. The code you are suggesting will have to be rewritten sometime
to support 32 bit pids.
The last time I checked, the only thing that stops the move back to
32-bit pids is a bug in the bash shell, and just a few workable IPC
interfaces and libc breakages.
Are 32 bit pids planned for 2.5?
next prev parent reply other threads:[~2002-04-20 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 9:15 lenny lv
2002-04-20 9:59 ` Dan Aloni [this message]
2002-04-20 17:50 Dan Kegel
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=1019296776.24728.40.camel@callisto.yi.org \
--to=da-x@gmx.net \
--cc=lennylv@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang@suda.edu.cn \
/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®