public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Waiman Long <Waiman.Long@hp.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Darren Hart <dvhart@linux.intel.com>,
	Davidlohr Bueso <davidlohr@hp.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-doc@vger.kernel.org, Jason Low <jason.low2@hp.com>,
	Scott J Norton <scott.norton@hp.com>
Subject: Re: [RFC PATCH 0/5] futex: introduce an optimistic spinning futex
Date: Wed, 23 Jul 2014 09:25:46 +0200	[thread overview]
Message-ID: <1406100346.5076.98.camel@marge.simpson.net> (raw)
In-Reply-To: <20140723065736.GM3935@laptop>

On Wed, 2014-07-23 at 08:57 +0200, Peter Zijlstra wrote: 
> On Wed, Jul 23, 2014 at 06:55:03AM +0200, Mike Galbraith wrote:
> > On Mon, 2014-07-21 at 09:42 -0700, Andi Kleen wrote:
> > 
> > > FWIW the main problem is currently that switch-through-idle is so 
> > > slow. I think improving that would give a boost to far more
> > > situations.
> > 
> > Two high frequency idle enter/exit suckage spots:
> > 
> > 1) nohz (tick) - it's expensive to start/stop tick on every micro-idle,
> > throttle it or something.
> 
> Yeah, so the idea was to use the cpuidle idle guestimator to control
> this, and now that we've moved it somewhat closer to the scheduler that
> might become possible.
> 
> > 2) ondemand governor - tweak silly default settings to reflect the
> > reality that we routinely schedule communicating threads cross core.
> 
> Yeah, so the plan is to shoot cpufreq in the head and base the
> replacement on smp aware metrics ;-) Its on a todo list somewhere..

It never ceases to amaze me that people aren't screaming bloody murder
about those two spots.  Watching performance of lightly loaded boxen is
enough to make a grown man cry.

SUSE (and I in all of my many regression testing trees) puts tourniquets
on both of these blood spurting gashes, laptops be damned.

I also resurrect mwait_idle(), as while you may consider it obsolete, I
still love my lovely little Q6600 box (power sucking pig) dearly :)

-Mike


  reply	other threads:[~2014-07-23  7:25 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 15:24 [RFC PATCH 0/5] futex: introduce an optimistic spinning futex Waiman Long
2014-07-21 15:24 ` [RFC PATCH 1/5] futex: add new exclusive lock & unlock command codes Waiman Long
2014-07-21 16:42   ` Thomas Gleixner
2014-07-22 18:22     ` Waiman Long
2014-07-22 21:00       ` Thomas Gleixner
2014-07-21 15:24 ` [RFC PATCH 2/5] futex: add optimistic spinning to FUTEX_SPIN_LOCK Waiman Long
2014-07-21 17:15   ` Davidlohr Bueso
2014-07-22 18:46     ` Waiman Long
2014-07-21 20:17   ` Jason Low
2014-07-22 19:34     ` Waiman Long
2014-07-21 15:24 ` [RFC PATCH 3/5] spinning futex: move a wakened task to spinning Waiman Long
2014-07-21 15:24 ` [RFC PATCH 4/5] spinning futex: put waiting tasks in a sorted rbtree Waiman Long
2014-07-21 15:24 ` [RFC PATCH 5/5] futex, doc: add a document on how to use the spinning futexes Waiman Long
2014-07-21 15:45   ` Randy Dunlap
2014-07-22  3:19     ` Waiman Long
2014-07-21 16:42 ` [RFC PATCH 0/5] futex: introduce an optimistic spinning futex Andi Kleen
2014-07-21 16:45   ` Andi Kleen
2014-07-21 17:20     ` Darren Hart
     [not found]     ` <CFF29A00.9D44A%dvhart@linux.intel.com>
2014-07-21 17:41       ` Darren Hart
2014-07-21 20:16         ` Thomas Gleixner
2014-07-21 21:27           ` Peter Zijlstra
2014-07-21 21:31             ` Andy Lutomirski
2014-07-21 21:47               ` Thomas Gleixner
2014-07-21 22:41                 ` Darren Hart
2014-07-22  1:01                   ` Thomas Gleixner
2014-07-22  1:34                     ` Steven Rostedt
2014-07-22  2:31                       ` Mike Galbraith
2014-07-22  3:06                       ` Davidlohr Bueso
2014-07-22  7:47                       ` Peter Zijlstra
2014-07-22  8:39                         ` Thomas Gleixner
2014-07-22  8:48                           ` Peter Zijlstra
2014-07-22  9:59                             ` Thomas Gleixner
2014-07-22 20:25                               ` Waiman Long
2014-07-22 20:52                                 ` Thomas Gleixner
2014-07-22 20:21                     ` Waiman Long
2014-07-22 21:03                       ` Thomas Gleixner
2014-07-22  0:32               ` Davidlohr Bueso
2014-07-22  7:35                 ` Peter Zijlstra
2014-07-21 21:43             ` Thomas Gleixner
2014-07-21 18:24     ` Thomas Gleixner
2014-07-22 18:35     ` Waiman Long
2014-07-22 18:28   ` Waiman Long
2014-07-23  4:55   ` Mike Galbraith
2014-07-23  6:57     ` Peter Zijlstra
2014-07-23  7:25       ` Mike Galbraith [this message]
2014-07-23  7:35         ` Peter Zijlstra
2014-07-23  7:39           ` Mike Galbraith
2014-07-23  7:52             ` Peter Zijlstra
2014-07-21 21:18 ` Ingo Molnar
2014-07-21 21:41   ` Thomas Gleixner
2014-07-22 19:36   ` Waiman Long

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=1406100346.5076.98.camel@marge.simpson.net \
    --to=umgwanakikbuti@gmail.com \
    --cc=Waiman.Long@hp.com \
    --cc=andi@firstfloor.org \
    --cc=davidlohr@hp.com \
    --cc=dvhart@linux.intel.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jason.low2@hp.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=scott.norton@hp.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