All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] srcu: Debloat the <linux/rcu_segcblist.h> header
Date: Tue, 2 May 2017 05:56:48 -0700	[thread overview]
Message-ID: <20170502125648.GA1286@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170502102503.GV3956@linux.vnet.ibm.com>

On Tue, May 02, 2017 at 03:25:03AM -0700, Paul E. McKenney wrote:
> On Tue, May 02, 2017 at 10:31:18AM +0200, Ingo Molnar wrote:
> > 
> > * Ingo Molnar <mingo@kernel.org> wrote:
> > 
> > > > I will get rid of the unused rcu_segcblist_extract_all() function and create a 
> > > > kernel/rcu/segcblist.c for the functions that are either non-trivial or 
> > > > performance-insensitive.
> > > > 
> > > > Does that cover it, or am I missing something?
> > > 
> > > I'd also suggest moving as much of the RCU internal data types into kernel/rcu/ 
> > > as possible. It's not clear to me which part of it is supposed to be a public 
> > > API and which bits are internal. It might make sense to keep it internal for the 
> > > time being, and only export things once there are users.
> > > 
> > > I.e. a pretty good solution would be to move all of 
> > > include/linux/rcu_segcblist.h to kernel/rcu/rcu_segcblist.c or so - and do a 
> > > kernel/rcu/rcu_segcblist.h with the data types and function prototypes.
> > 
> > I.e. the attached patch as a first step.
> > 
> > Only minimally build tested, but it appears to be do the trick.
> > 
> > This changes the <linux/rcu_segcblist.h> header from ~700 lines to only 90 lines - 
> > 60% of which is comments.
> > 
> > The deinlining of the inline functions within kernel/rcu/ should also be done, as 
> > a separate patch on top of this.
> > 
> > What do you think?
> 
> Thank you very much!
> 
> I have pulled this in and started a short rcutorture run.  I will do
> de-inline and create a .c file on top of this and retest after the
> rcutorture has finished.

And I am applying the following fixlet for !SMP builds, which I am
retesting.  Other than that, initial rcutorture ran fine!

							Thanx, Paul

------------------------------------------------------------------------

diff --git a/kernel/rcu/srcutiny.c b/kernel/rcu/srcutiny.c
index b8293527ee18..36e1f82faed1 100644
--- a/kernel/rcu/srcutiny.c
+++ b/kernel/rcu/srcutiny.c
@@ -30,6 +30,7 @@
 #include <linux/srcu.h>
 
 #include <linux/rcu_node_tree.h>
+#include "rcu_segcblist.h"
 #include "rcu.h"
 
 static int init_srcu_struct_fields(struct srcu_struct *sp)

  reply	other threads:[~2017-05-02 12:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01  9:59 [GIT PULL] RCU changes for v4.12 Ingo Molnar
2017-05-02  1:19 ` Linus Torvalds
2017-05-02  4:02   ` Paul E. McKenney
2017-05-02  4:11     ` Linus Torvalds
2017-05-02  4:30       ` Paul E. McKenney
2017-05-02  7:59     ` Ingo Molnar
2017-05-02  8:31       ` [PATCH] srcu: Debloat the <linux/rcu_segcblist.h> header Ingo Molnar
2017-05-02 10:25         ` Paul E. McKenney
2017-05-02 12:56           ` Paul E. McKenney [this message]
2017-05-09  7:26 ` [RFC GIT PULL, v2] RCU changes for v4.12 Ingo Molnar
2017-05-10 17:27   ` Linus Torvalds
2017-05-10 19:54     ` Ingo Molnar
2017-05-10 20:01       ` Linus Torvalds
2017-05-11  6:54         ` Ingo Molnar
2017-05-10 19:54     ` Paul E. McKenney
2017-05-10 20:17       ` Linus Torvalds
2017-05-10 20:51         ` Paul E. McKenney
2017-05-10 21:08           ` Linus Torvalds
2017-05-10 22:53             ` Paul E. McKenney

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=20170502125648.GA1286@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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 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.