From: Clark Williams <williams@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCHv2 0/2] move sysctl bits into new header and add a SCHED_RR tuning knob
Date: Thu, 31 Jan 2013 13:52:25 -0600 [thread overview]
Message-ID: <20130131135225.6f32af1a@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Ingo,
On your suggestion, I created the directory include/linux/sched and created
include/linux/sched/sysctl.h, which contains all the sysctl scheduler bits (plus a
few autogroup prototype definitions). If there are still objections we can create
autogroup.h or some other more generic entry in include/linux/sched and move them
there (or even back to include/linux/sched.h).
The second patch is just adding the SCHED_RR tuning knob to the new sysctl header
and the code changes to core.c, rt.c and sysctl.c.
I saw a few other things that might be candidates for a new file in the sched dir,
things like NO_HZ and CGROUPS but wanted to get this in place first.
Clark Williams (2):
sched: create new scheduler include dir and move sysctl defs there
sched/rt: add a tuning knob to allow changing SCHED_RR timeslice
include/linux/sched.h | 108 +------------------------------------
include/linux/sched/sysctl.h | 126 +++++++++++++++++++++++++++++++++++++++++++
kernel/sched/core.c | 19 +++++++
kernel/sched/rt.c | 6 ++-
kernel/sysctl.c | 8 +++
5 files changed, 158 insertions(+), 109 deletions(-)
create mode 100644 include/linux/sched/sysctl.h
--
1.7.11.7
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2013-01-31 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130131135225.6f32af1a@redhat.com \
--to=williams@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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