mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "Shi, Alex" <alex.shi@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"efault@gmx.de" <efault@gmx.de>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:sched/urgent] sched: Fix select_idle_sibling() regression in selecting an idle SMT sibling
Date: Wed, 21 Dec 2011 18:03:13 -0800	[thread overview]
Message-ID: <1324519393.21294.20.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <1324517502.17054.174.camel@debian>

On Wed, 2011-12-21 at 17:31 -0800, Shi, Alex wrote:
> This patch partly fixed a performance regression that triggered by
> 4dcfe1025b513c2c, but issue still exists.

So how much was the regression caused by the commit 4dcfe1025b513c2c and
how much did we recover with this fix I posted. If we are talking about
the regression caused by this single commit 4dcfe1025b513c2c, then I
don't know of any other related fixes other than the recent fix we
pushed upstream (ab2789213d224202237292d78aaa0c386c7b28b2).

thanks,
suresh


  reply	other threads:[~2011-12-22  1:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 19:47 [patch] sched: fix " Suresh Siddha
2011-12-16  8:44 ` Ingo Molnar
2011-12-16 11:36 ` [tip:sched/urgent] sched: Fix " tip-bot for Peter Zijlstra
2011-12-21 12:33   ` alex shi
2011-12-21 12:52     ` Peter Zijlstra
2011-12-21 19:42       ` Suresh Siddha
2011-12-22  1:31         ` Alex,Shi
2011-12-22  2:03           ` Suresh Siddha [this message]
2011-12-22  2:16             ` Alex,Shi
2011-12-22  6:59               ` Alex,Shi
2011-12-23 18:43               ` Suresh Siddha
2011-12-24  7:04                 ` Shi, Alex
2012-01-06  8:14                 ` Alex,Shi

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=1324519393.21294.20.camel@sbsiddha-desk.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=alex.shi@intel.com \
    --cc=efault@gmx.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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®