From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] some scheduler code movements and small cleanup
Date: Wed, 21 Jun 2017 09:23:55 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1706210923120.29475@knanqh.ubzr> (raw)
In-Reply-To: <20170614171926.8345-1-nicolas.pitre@linaro.org>
Ping.
On Wed, 14 Jun 2017, Nicolas Pitre wrote:
> On Tue, 13 Jun 2017, Ingo Molnar wrote:
>
> > So I'm fine with most of the code movement - let's try this series
> > without any of the more controversial bits which should make future
> > arguments easier.
>
> Here it is. Big diffstat due to code movement which should untangle
> scheduler classes from common code some more, and isolating PI futex
> support, with the net effect of reducing the common code file size.
>
> Sidenote: I just discovered that the default git diff algorithm produces
> awful results with this series at least, with 1270 extra diff lines
> compared to the output from the patience or minimal diff algorithms.
> Using --diff-algorithm=minimal produces a much saner diffstat, way more
> representative of the actual changes in this case.
>
>
> include/linux/futex.h | 7 +-
> init/Kconfig | 8 +-
> kernel/futex.c | 1559 +---------------------------------------
> kernel/futex_pi.c | 1563 +++++++++++++++++++++++++++++++++++++++++
> kernel/sched/core.c | 655 +----------------
> kernel/sched/deadline.c | 336 +++++++++
> kernel/sched/rt.c | 310 ++++++++
> kernel/sched/sched.h | 19 +
> 8 files changed, 2272 insertions(+), 2185 deletions(-)
>
next prev parent reply other threads:[~2017-06-21 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:19 [PATCH 0/4] some scheduler code movements and small cleanup Nicolas Pitre
2017-06-14 17:19 ` [PATCH 1/4] cpuset/sched: cpuset makes sense for SMP only Nicolas Pitre
2017-06-23 13:58 ` [tip:sched/core] sched/cpuset: Only offer CONFIG_CPUSETS if SMP is enabled tip-bot for Nicolas Pitre
2017-06-14 17:19 ` [PATCH 2/4] sched/deadline: move dl related code out of sched/core.c Nicolas Pitre
2017-06-14 17:19 ` [PATCH 3/4] sched/rt: move rt " Nicolas Pitre
2017-06-21 13:23 ` Nicolas Pitre [this message]
2017-06-21 16:46 ` [PATCH 0/4] some scheduler code movements and small cleanup Ingo Molnar
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=alpine.LFD.2.20.1706210923120.29475@knanqh.ubzr \
--to=nicolas.pitre@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).