All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex,Shi" <alex.shi@intel.com>
To: "Siddha, Suresh B" <suresh.b.siddha@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: Thu, 22 Dec 2011 09:31:42 +0800	[thread overview]
Message-ID: <1324517502.17054.174.camel@debian> (raw)
In-Reply-To: <1324496556.21294.11.camel@sbsiddha-desk.sc.intel.com>


> > > Even with this fix, the loopback netperf testing TCP-RR, still have
> > > about 5% regresion on our 2 socket * 8 cores SNB machine.
> > > which is your patchset includes all cleaning? wondering if that is helpful.
> > 
> > Sorry, but that question fails to parse here. What were you asking?

This patch partly fixed a performance regression that triggered by
4dcfe1025b513c2c, but issue still exists.
> 
> Yes Alex. You need to elaborate your question. Regression to what kernel
> etc?
> 
> Also there is another known issue that's been addressed in -tip. Here is
> that patch. https://lkml.org/lkml/2011/12/21/137

Thanks! 
I am testing whole tip changes against 3.2-rc6. On the 4dcfe1025b513c2c
commit, seems interrupts is abnormal. So maybe above fix is suit for
this issue. wait the results. 




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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 19:47 [patch] sched: fix select_idle_sibling() regression in selecting an idle SMT sibling 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 [this message]
2011-12-22  2:03           ` Suresh Siddha
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=1324517502.17054.174.camel@debian \
    --to=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=suresh.b.siddha@intel.com \
    --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 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.