[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1324517502.17054.174.camel@debian>
Date: Thu, 22 Dec 2011 09:31:42 +0800
From: "Alex,Shi" <alex.shi@...el.com>
To: "Siddha, Suresh B" <suresh.b.siddha@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"efault@....de" <efault@....de>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...e.hu" <mingo@...e.hu>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:sched/urgent] sched: Fix select_idle_sibling() regression
in selecting an idle SMT sibling
> > > 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists