From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] futex: split PI support to a file of its own
Date: Tue, 1 Aug 2017 00:23:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1708010011390.5981@knanqh.ubzr> (raw)
In-Reply-To: <alpine.DEB.2.20.1707310948230.2314@nanos>
On Mon, 31 Jul 2017, Thomas Gleixner wrote:
> But I really do not agree with your reasoning about easier to understand
> and maintain. I have the dubious pleasure to stare into that code on a
> regular base. PI and non PI share a lot of code and it's really not helping
> to have two separate files to stare at. That makes following the PI code
> even harder than it is already. So I rather like to see that PI code in an
> #ifdef block and not split out into its own file.
OK. And in fact I think I now managed to keep #ifdef's to a very small
number, counting on dead code elimination instead. Please see next
patch.
> Please provide a diffstat along with the patch next time.
Hmmm... was supposed to be there. For the record it was:
include/linux/futex.h | 7 +-
init/Kconfig | 7 +-
kernel/futex.c | 1559 +-----------------------------------------
kernel/futex_pi.c | 1563 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 1598 insertions(+), 1538 deletions(-)
Admitedly not small. But when PI is disabled then futex.o shrinks by
roughly the half of its original size. So a lot of code is dedicated to
PI.
Nicolas
prev parent reply other threads:[~2017-08-01 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 4:45 Nicolas Pitre
2017-07-31 7:58 ` Thomas Gleixner
2017-08-01 4:23 ` Nicolas Pitre [this message]
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.1708010011390.5981@knanqh.ubzr \
--to=nicolas.pitre@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®