public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: lkml <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Dimitri Sivanich <sivanich@sgi.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	dipankar@in.ibm.com, josh@freedesktop.org,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] sched/core: implement and cpuhog
Date: Fri, 02 Apr 2010 15:16:46 +0900	[thread overview]
Message-ID: <4BB58BCE.8090106@kernel.org> (raw)

Hello, Ingo.

Can you please pull from the following git tree into sched/core to
receive cpuhog patches?

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git cpuhog

Both sched/core and the patches remained the same from the second
take[2].  Rusty Russell acked stop_machine changes and Oleg likes the
changes.

Peter agrees with the mechanics but is unhappy with the naming and
suggests using stop_cpu/machine() names instead.  Currently, visible
API is

* hog_one_cpu()
* hog_cpus()
* [__]stop_machine()

IIUC, Peter is suggesting something like (please feel free to correct
if I got it wrong)

* stop_one_cpu()
* stop_cpus()
* [__]stop_machine()

The renaming shouldn't be difficult one way or the other but I think
hog is better because it better describes what the API does (it
doesn't really stop the cpu or cpus).  Please refer to the discussions
in the first take[1] and second take[2] for details.

The branch contains the following changes.

Tejun Heo (4):
      cpuhog: implement cpuhog
      stop_machine: reimplement using cpuhog
      scheduler: replace migration_thread with cpuhog
      scheduler: kill paranoia check in synchronize_sched_expedited()

 Documentation/RCU/torture.txt |   10 -
 arch/s390/kernel/time.c       |    1 -
 drivers/xen/manage.c          |   14 +--
 include/linux/cpuhog.h        |   24 +++
 include/linux/rcutiny.h       |    2 -
 include/linux/rcutree.h       |    1 -
 include/linux/stop_machine.h  |   20 ---
 kernel/Makefile               |    2 +-
 kernel/cpu.c                  |    8 -
 kernel/cpuhog.c               |  368 +++++++++++++++++++++++++++++++++++++++++
 kernel/module.c               |   14 +--
 kernel/rcutorture.c           |    2 +-
 kernel/sched.c                |  282 ++++++--------------------------
 kernel/sched_fair.c           |   39 +++--
 kernel/stop_machine.c         |  162 +++++--------------
 15 files changed, 511 insertions(+), 438 deletions(-)
 create mode 100644 include/linux/cpuhog.h
 create mode 100644 kernel/cpuhog.c

Thanks.

-- 
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/958743
[2] http://thread.gmane.org/gmane.linux.kernel/962635

             reply	other threads:[~2010-04-02  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02  6:16 Tejun Heo [this message]
2010-04-02  6:18 ` [GIT PULL] sched/core: implement and *use* cpuhog Tejun Heo

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=4BB58BCE.8090106@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=dipankar@in.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=josh@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sivanich@sgi.com \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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