public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: alex shi <lkml.alex@gmail.com>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	efault@gmx.de, alex.shi@intel.com, suresh.b.siddha@intel.com,
	tglx@linutronix.de, mingo@elte.hu,
	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 13:52:24 +0100	[thread overview]
Message-ID: <1324471944.10752.8.camel@twins> (raw)
In-Reply-To: <CAGjg+kEOkkjnQQJJyGQzGApV5asM5oqvRwEr2VkJy9G5gg1rxw@mail.gmail.com>

On Wed, 2011-12-21 at 20:33 +0800, alex shi wrote:
> > Fix it. Slightly bigger patch of cleaning all these goto's etc
> > is queued up for the next release.
> >
> 
> 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?

  reply	other threads:[~2011-12-21 12:52 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 [this message]
2011-12-21 19:42       ` Suresh Siddha
2011-12-22  1:31         ` Alex,Shi
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=1324471944.10752.8.camel@twins \
    --to=peterz@infradead.org \
    --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=lkml.alex@gmail.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox