From: Peter Zijlstra <peterz@infradead.org>
To: Sergey Oboguev <oboguev.public@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH 1/2] sched: deferred set priority (dprio) -- rebased for the tip
Date: Fri, 26 Sep 2014 15:23:30 +0200 [thread overview]
Message-ID: <20140926132330.GF4140@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+80gGaC5tutmFiTCyL-zoBY4BcbZnh63wXhO-g5UetP+w5g4w@mail.gmail.com>
On Thu, Sep 25, 2014 at 12:26:04PM -0700, Sergey Oboguev wrote:
> This is a replica of "[PATCH 1/2] dprio" (posted yesterday for 3.16.3)
> rebased now for the current tip (3.17.0-rc6).
>
> Signed-off-by: Sergey Oboguev <oboguev@yahoo.com>
>
> ---
> Documentation/sysctl/kernel.txt | 14 +
> fs/exec.c | 8 +
> include/linux/dprio.h | 129 +++++++++
> include/linux/init_task.h | 17 ++
> include/linux/sched.h | 19 ++
> include/uapi/linux/Kbuild | 1 +
> include/uapi/linux/capability.h | 5 +-
> include/uapi/linux/dprio_api.h | 137 +++++++++
> include/uapi/linux/prctl.h | 2 +
> init/Kconfig | 2 +
> kernel/Kconfig.dprio | 68 +++++
> kernel/exit.c | 6 +
> kernel/fork.c | 88 +++++-
> kernel/sched/Makefile | 1 +
> kernel/sched/core.c | 195 ++++++++++++-
> kernel/sched/dprio.c | 617 ++++++++++++++++++++++++++++++++++++++++
> kernel/sys.c | 6 +
> kernel/sysctl.c | 12 +
> 18 files changed, 1315 insertions(+), 12 deletions(-)
2 lines of changelog for a ~1300 line patch, you must be kidding, right?
What problem is it solving and why do I care?
next prev parent reply other threads:[~2014-09-26 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 19:26 [PATCH 1/2] sched: deferred set priority (dprio) -- rebased for the tip Sergey Oboguev
2014-09-26 13:23 ` Peter Zijlstra [this message]
2014-09-26 15:02 ` Sergey Oboguev
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=20140926132330.GF4140@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oboguev.public@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.