public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Jones <davej@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] scheduler bits from 2.5.23-dj1
Date: Thu, 20 Jun 2002 11:17:29 -0700	[thread overview]
Message-ID: <20020620181729.GY22961@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206201929310.9805-100000@e2>

On Thu, Jun 20, 2002 at 07:31:18PM +0200, Ingo Molnar wrote:
> looks good to me - what do you think about my other pidhash suggestion:

An excellent idea. I didn't go all the way and make the pidhash entirely
private to fork.c but taking find_task_by_pid() out-of-line is implemented
in the following, built atop the prior patch. I can also privatize the
pidhash entirely if that's wanted.


Cheers,
Bill

diff -urN linux-2.5.23-virgin/include/linux/sched.h linux-2.5.23-wli/include/linux/sched.h
--- linux-2.5.23-virgin/include/linux/sched.h	Thu Jun 20 10:53:42 2002
+++ linux-2.5.23-wli/include/linux/sched.h	Thu Jun 20 10:55:18 2002
@@ -459,19 +459,7 @@
 	list_del(&p->pidhash_list);
 }
 
-static inline task_t *find_task_by_pid(int pid)
-{
-	list_t *p, *pid_list = &pidhash[pid_hashfn(pid)];
-
-	list_for_each(p, pid_list) {
-		task_t *t = list_entry(p, task_t, pidhash_list);
-
-		if(t->pid == pid)
-			return t;
-	}
-
-	return NULL;
-}
+extern task_t *find_task_by_pid(int pid);
 
 /* per-UID process charging. */
 extern struct user_struct * alloc_uid(uid_t);
diff -urN linux-2.5.23-virgin/kernel/fork.c linux-2.5.23-wli/kernel/fork.c
--- linux-2.5.23-virgin/kernel/fork.c	Thu Jun 20 10:53:42 2002
+++ linux-2.5.23-wli/kernel/fork.c	Thu Jun 20 10:55:55 2002
@@ -69,6 +69,21 @@
 		INIT_LIST_HEAD(&pidhash[i]);
 }
 
+task_t *find_task_by_pid(int pid)
+{
+	list_t *p, *pid_list = &pidhash[pid_hashfn(pid)];
+
+	list_for_each(p, pid_list) {
+		task_t *t = list_entry(p, task_t, pidhash_list);
+
+		if(t->pid == pid)
+			return t;
+	}
+
+	return NULL;
+}
+EXPORT_SYMBOL(find_task_by_pid);
+
 rwlock_t tasklist_lock __cacheline_aligned = RW_LOCK_UNLOCKED;  /* outer */
 
 void add_wait_queue(wait_queue_head_t *q, wait_queue_t * wait)

  parent reply	other threads:[~2002-06-20 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 11:23 Linux 2.5.23-dj1 Dave Jones
2002-06-19 23:36 ` [patch] scheduler bits from 2.5.23-dj1 Ingo Molnar
2002-06-19 23:47   ` Robert Love
2002-06-20  0:07     ` Andrea Arcangeli
2002-06-20  0:10       ` Robert Love
2002-06-19 23:47   ` Dave Jones
2002-06-20 17:20     ` William Lee Irwin III
2002-06-20 17:31       ` Ingo Molnar
2002-06-20 17:52         ` William Lee Irwin III
2002-06-20 18:17         ` William Lee Irwin III [this message]
2002-06-20 19:26           ` William Lee Irwin III
2002-06-21  1:34             ` William Lee Irwin III
2002-06-19 23:56   ` William Lee Irwin III
2002-06-20  7:26   ` Manik Raina
2002-06-20 13:13     ` Ingo Molnar
2002-06-20 13:34     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 10:11 Mikael Pettersson

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=20020620181729.GY22961@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox