public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Peter Williams <pwil3058@bigpond.net.au>,
	mingo@elte.hu, nickpiggin@yahoo.com.au,
	linux-kernel@vger.kernel.org
Subject: Re: smp 'nice' bias support breaks scheduler behavior
Date: Fri, 27 Jan 2006 12:54:53 +1100	[thread overview]
Message-ID: <200601271254.54009.kernel@kolivas.org> (raw)
In-Reply-To: <20060126173423.B19789@unix-os.sc.intel.com>

On Friday 27 January 2006 12:34, Siddha, Suresh B wrote:
> On Fri, Jan 27, 2006 at 12:29:02PM +1100, Con Kolivas wrote:
> > We planned to push it for 2.6.16 but issues showed up, which Peter has
> > since addressed - but this means the code has not had enough testing to
> > go into 2.6.16 - so it is likely to be in 2.6.17.
>
> Then for 2.6.16, I would like to see smp nice handling patch backed out.
>
> Do you agree?

It's not my decision to keep Peter's patch out of mainline. If you can make a 
strong enough case for it then Linus will merge it up even though it's after 
rc1. Otherwise I'll let Ingo decide on whether to pull the current 
implementation or not - you're saying that with the one thing you described 
that misbehaves that it is doing more harm than fixing smp nice handling.

Con

  reply	other threads:[~2006-01-27  1:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 10:52 smp 'nice' bias support breaks scheduler behavior Siddha, Suresh B
2006-01-26 12:25 ` Con Kolivas
2006-01-26 23:36   ` Peter Williams
2006-01-26 23:56     ` Siddha, Suresh B
2006-01-27  1:29       ` Con Kolivas
2006-01-27  1:34         ` Siddha, Suresh B
2006-01-27  1:54           ` Con Kolivas [this message]
2006-01-27  2:11             ` Siddha, Suresh B
2006-01-27  2:58               ` Con Kolivas

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=200601271254.54009.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pwil3058@bigpond.net.au \
    --cc=suresh.b.siddha@intel.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