public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stijn Devriendt <highguy@gmail.com>
Cc: Chris Mason <chris.mason@oracle.com>, Ingo Molnar <mingo@elte.hu>,
	axboe@kernel.dk, linux-kernel@vger.kernel.org,
	Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH RFC] reduce runqueue lock contention
Date: Fri, 04 Jun 2010 14:00:43 +0200	[thread overview]
Message-ID: <1275652843.27810.39750.camel@twins> (raw)
In-Reply-To: <AANLkTinifUTnjypY-h6Vv2qV9O7O4ZOFurxtrEr-3Rig@mail.gmail.com>

On Fri, 2010-06-04 at 12:56 +0200, Stijn Devriendt wrote:

> The issue I want to tackle is waking up processes when others go to sleep.
> This means try_to_wake_up() from inside the runqueue lock.


Tejun did something for that:

  http://lkml.org/lkml/2010/5/13/136
  


  reply	other threads:[~2010-06-04 12:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 20:48 [PATCH RFC] reduce runqueue lock contention Chris Mason
2010-05-20 21:09 ` Peter Zijlstra
2010-05-20 21:23   ` Peter Zijlstra
2010-05-20 22:17     ` Chris Mason
2010-05-20 22:21   ` Chris Mason
2010-06-04 10:56 ` Stijn Devriendt
2010-06-04 12:00   ` Peter Zijlstra [this message]
2010-06-05  9:37     ` Stijn Devriendt
2010-06-21 10:02 ` Peter Zijlstra
2010-06-21 10:54   ` Peter Zijlstra
2010-06-21 13:04     ` Peter Zijlstra
2010-06-22 13:33       ` Peter Zijlstra
2010-06-22 21:11         ` Ingo Molnar
2010-06-23  9:10           ` Peter Zijlstra
2010-12-01 23:13             ` Frank Rowand
2010-12-02  1:17               ` Frank Rowand
2010-12-02  7:36               ` Peter Zijlstra
2010-12-14  2:41       ` Frank Rowand
2010-12-14  3:42         ` Mike Galbraith
2010-12-14 21:42           ` Frank Rowand
2010-12-15 18:59         ` Oleg Nesterov

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=1275652843.27810.39750.camel@twins \
    --to=peterz@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=chris.mason@oracle.com \
    --cc=highguy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@kernel.org \
    /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