[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1324519393.21294.20.camel@sbsiddha-desk.sc.intel.com>
Date: Wed, 21 Dec 2011 18:03:13 -0800
From: Suresh Siddha <suresh.b.siddha@...el.com>
To: "Shi, Alex" <alex.shi@...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
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
--
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