From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, pjt@google.com, cl@linux.com,
riel@redhat.com, bharata.rao@gmail.com,
akpm@linux-foundation.org, Lee.Schermerhorn@hp.com,
aarcange@redhat.com, danms@us.ibm.com, suresh.b.siddha@intel.com,
tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/numa] sched: Make find_busiest_queue a method
Date: Fri, 18 May 2012 16:56:48 +0200 [thread overview]
Message-ID: <1337353008.573.49.camel@twins> (raw)
In-Reply-To: <tip-3n9wqw2rdmhtu7qjhpoegh7u@git.kernel.org>
On Fri, 2012-05-18 at 03:36 -0700, tip-bot for Peter Zijlstra wrote:
> sched: Make find_busiest_queue a method
>
> Its a bit awkward but it was the least painful means of modifying the
> queue selection. Used in a later patch to conditionally use a random
> queue.
>
> ---
> include/linux/mm_types.h | 8 +
> include/linux/sched.h | 14 +
> init/Kconfig | 2 +-
> kernel/fork.c | 2 +
> kernel/sched/Makefile | 1 +
> kernel/sched/core.c | 22 ++-
> kernel/sched/debug.c | 3 +
> kernel/sched/fair.c | 257 +++++++++++++++--
> kernel/sched/features.h | 12 +
> kernel/sched/numa.c | 741 ++++++++++++++++++++++++++++++++++++++++++++++
> kernel/sched/sched.h | 34 +++
> mm/init-mm.c | 10 +
> 12 files changed, 1079 insertions(+), 27 deletions(-)
Something went wrong here.. this were 3 patches:
Subject: sched: Make find_busiest_queue a method
Subject: sched: Implement home-node awareness
Subject: sched, numa: Numa balancer
next prev parent reply other threads:[~2012-05-18 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 10:36 tip-bot for Peter Zijlstra
2012-05-18 14:56 ` Peter Zijlstra [this message]
2012-05-19 11:05 ` Ingo Molnar
2012-09-28 7:59 [tip:sched/numa] sched: Make find_busiest_queue() " tip-bot for 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=1337353008.573.49.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=Lee.Schermerhorn@hp.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bharata.rao@gmail.com \
--cc=cl@linux.com \
--cc=danms@us.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjt@google.com \
--cc=riel@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome