public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	wli@holomorphy.com
Subject: Re: [patch] scheduler bits from 2.5.23-dj1
Date: Thu, 20 Jun 2002 01:47:29 +0200	[thread overview]
Message-ID: <20020620014729.X29373@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0206200123470.25434-100000@e2>; from mingo@elte.hu on Thu, Jun 20, 2002 at 01:35:35AM +0200

On Thu, Jun 20, 2002 at 01:35:35AM +0200, Ingo Molnar wrote:

Hi Ingo,

 > the scheduler optimisation in 2.5.23-dj1, from James Bottomley, look fine
 > to me. I did some modifications:

Thanks for taking time out to look them over..
The bulk of the UP optimisation was by Mikael Petterson, James just
fixed up something I goofed in an earlier patchset.


 >  - there is no need for the #if CONFIG_SMP, gcc is good at optimizing away
 >    a branch if it has a (0 != 0) condition on UP :-)

*nod*, I had intended to clean this up, but there's only so many hours
in a day.. 8-)

 > another change in 2.5.23-dj1 is the initialization of the pidhash in
 > sched_init(). It does not belong there - please create a new init function
 > within fork.c if needed. The pidhash init used to be in sched_init(), but
 > this doesnt make it right.

Agreed.

 > And i'm not quite sure whether it's needed to expose the pidhash to the
 > rest of the kernel - it would be much simpler to have it in kernel/fork.c
 > locally, and find_task_by_pid() would be a function instead of an inline.
 > (it has a ~49 bytes footprint on x86, it's rather heavy i think.)

I'll take a look at this tomorrow, unless William "no sleep `til 2.6" Irwin
beats me to it 8-)  (he did this part of the patch iirc).

 > my current scheduler patchset (against 2.5.23, tested) is attached.

Thanks again.
 
    Dave.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  parent reply	other threads:[~2002-06-19 23:47 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 [this message]
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
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=20020620014729.X29373@suse.de \
    --to=davej@suse.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.com \
    --cc=wli@holomorphy.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