From: alad@hss.hns.com
To: linux-kernel@vger.kernel.org
Subject: get_pid() : enahancement
Date: Wed, 4 Apr 2001 12:00:58 +0530 [thread overview]
Message-ID: <65256A24.00233ECF.00@sandesh.hss.hns.com> (raw)
In 2.4 kernel we now have no limit on the number of tasks running on a system
(no NR_TASKS anymore)...
I was just wondering on the efficiency of get_pid() implemetation... Although
'next_safe' concept in this function seems useful but I think we now need a
robust PID allocator..
We can have a discussion so that get_pid() can be made more effecient in future
kernel.
Amol
next reply other threads:[~2001-04-04 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 6:30 alad [this message]
2001-04-04 11:05 ` Alan Cox
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=65256A24.00233ECF.00@sandesh.hss.hns.com \
--to=alad@hss.hns.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®