mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 0/2] RFC: readd fair sleepers for server systems
Date: Tue, 22 May 2012 10:53:42 +0200	[thread overview]
Message-ID: <1337676822.5446.3.camel@marge.simpson.net> (raw)
In-Reply-To: <4FBB3C35.1040104@linux.vnet.ibm.com>

On Tue, 2012-05-22 at 09:11 +0200, Christian Ehrhardt wrote: 
> 
> On 05/21/2012 08:17 PM, Mike Galbraith wrote:
> > On Mon, 2012-05-21 at 17:45 +0200, Martin Schwidefsky wrote:
> >> our performance team found a performance degradation with a recent
> >> distribution update in regard to fair sleepers (or the lack of fair
> >> sleepers). On s390 we used to run with fair sleepers disabled.
> >>
> >> We see the performance degradation with our network benchmark and fair
> >> sleepers enabled, the largest hit is on virtual connections:
> >
> > I can see you wanting the feature back.  You guys apparently do not
> > generally run mixed loads on your boxen, else you wouldn't want to turn
> > the scheduler into a tick granularity scheduler, but why compile time?
> > If the fast path branch isn't important, and given it only became
> > important while I was trying to scrape a few cycles together, why not
> > just restore the feature as it used to exist under the pretext that you
> > need it, and others may as well, so we eat the branch in the interest of
> > general flexibility, and call removal a booboo?
> >
> > -Mike
> >
> 
> If "eating the branches" is fine for everyone s390 can surely live with 
> it. The intention to make it configurable, was to allow systems that 
> really never want it, to be still able to avoid the branch.
> 
> By that everyone can configure it the way they want it and we avoid 
> another modification of the same code over and over again.

Ok.  Features have become cheaper, but we can still use every cycle we
can get our grubby mitts on.

-Mike



  reply	other threads:[~2012-05-22  8:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 15:45 Martin Schwidefsky
2012-05-21 15:45 ` [PATCH 1/2] sched: readd FAIR_SLEEPERS feature Martin Schwidefsky
2012-05-22  7:11   ` Christian Ehrhardt
2012-05-22  9:06     ` Mike Galbraith
2012-05-21 15:45 ` [PATCH 2/2] sched: enable FAIR_SLEEPERS for s390 Martin Schwidefsky
2012-05-21 18:17 ` [PATCH 0/2] RFC: readd fair sleepers for server systems Mike Galbraith
2012-05-22  7:11   ` Christian Ehrhardt
2012-05-22  8:53     ` Mike Galbraith [this message]
2012-05-22  9:01 ` Peter Zijlstra
2012-05-23 11:32   ` Christian Ehrhardt
2012-05-23 11:49     ` Peter Zijlstra
2012-05-23 15:28       ` Christian Ehrhardt
2012-05-23 15:43         ` Peter Zijlstra

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=1337676822.5446.3.camel@marge.simpson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=schwidefsky@de.ibm.com \
    /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

Powered by JetHome