From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrew Morton <akpm@zip.com.au>,
Paul Larson <plars@austin.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
davej@suse.de, frankeh@us.ibm.com, andrea@suse.de
Subject: Re: [PATCH] Linux-2.5 fix/improve get_pid()
Date: Thu, 8 Aug 2002 14:45:17 -0700 [thread overview]
Message-ID: <20020808214517.GH15685@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208081312330.8705-100000@home.transmeta.com>
On Thu, Aug 08, 2002 at 01:24:35PM -0700, Linus Torvalds wrote:
> Without that per-pid-count thing clarified, I don't think the (otherwise
> fairly straightforward) approach of Bills really flies.
I implemented the rest of it, based on maintaining hashtables for the
tgid, pgid, and sid as well as the pid itself. get_pid() was not the
focus of it.
Cheers,
Bill
next prev parent reply other threads:[~2002-08-08 21:41 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 22:03 [PATCH] Linux-2.5 fix/improve get_pid() Paul Larson
2002-08-07 23:06 ` Andrew Morton
2002-08-08 0:24 ` Andries Brouwer
2002-08-08 19:42 ` William Lee Irwin III
2002-08-08 20:47 ` Andries Brouwer
2002-08-09 11:22 ` Analysis for Linux-2.5 fix/improve get_pid(), comparing various approaches Hubertus Franke
2002-08-09 15:36 ` Andries Brouwer
2002-08-09 18:14 ` Hubertus Franke
2002-08-09 16:05 ` Linus Torvalds
2002-08-09 18:18 ` Hubertus Franke
2002-08-08 20:24 ` [PATCH] Linux-2.5 fix/improve get_pid() Linus Torvalds
2002-08-08 21:30 ` H. Peter Anvin
2002-08-08 21:45 ` William Lee Irwin III [this message]
2002-08-09 4:42 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:56 Hubertus Franke
2002-08-08 19:15 ` Rik van Riel
2002-08-08 19:18 ` Paul Larson
2002-08-08 21:43 Hubertus Franke
2002-08-08 22:02 ` Linus Torvalds
2002-08-08 22:26 ` Linus Torvalds
2002-08-08 23:09 ` Albert D. Cahalan
2002-08-09 3:26 ` Chris Adams
2002-08-09 7:04 ` Albert D. Cahalan
2002-08-09 8:48 ` Helge Hafting
2002-08-09 10:32 ` Alan Cox
2002-08-09 9:35 ` Andrew Morton
2002-08-09 10:37 ` Andries Brouwer
2002-08-09 13:00 ` Chris Adams
2002-08-09 14:39 ` Albert D. Cahalan
2002-08-09 13:59 ` Rik van Riel
2002-08-09 14:57 ` Albert D. Cahalan
2002-08-08 22:34 ` Paul Larson
2002-08-08 22:44 ` Rik van Riel
2002-08-08 22:37 ` Rik van Riel
2002-08-09 1:49 ` Andries Brouwer
2002-08-09 19:34 ` Paul Larson
2002-08-09 20:13 ` Paul Larson
2002-08-09 20:40 ` Andries Brouwer
2002-08-09 21:23 ` Linus Torvalds
2002-08-09 21:42 ` Linus Torvalds
2002-08-09 21:46 ` Paul Larson
2002-08-09 22:04 ` Linus Torvalds
2002-08-10 17:23 ` Jamie Lokier
2002-08-10 18:33 ` Linus Torvalds
2002-08-10 18:48 ` Jamie Lokier
2002-08-11 20:41 ` Alan Cox
2002-08-11 19:58 ` Jamie Lokier
2002-08-11 21:23 ` Alan Cox
2002-08-11 20:10 ` Jamie Lokier
2002-08-12 8:56 ` Padraig Brady
2002-08-12 10:37 ` Alan Cox
2002-08-12 9:21 ` Padraig Brady
2002-08-12 14:40 ` Paul Larson
2002-08-08 21:50 Hubertus Franke
2002-08-09 0:53 Hubertus Franke
2002-08-12 16:15 Jim Houston
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=20020808214517.GH15685@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=davej@suse.de \
--cc=frankeh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.com \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.