All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/2] Debloat rcu_segcblist header file
Date: Tue, 2 May 2017 08:35:42 -0700	[thread overview]
Message-ID: <20170502153542.GA19274@linux.vnet.ibm.com> (raw)

Hello!

This series debloats the include/linux/rcu_segcblist.h include file:

1.	Leave data structures in include/linux/rcu_segcblist.h, but
	move functions to kernel/rcu/rcu_segcblist.h, courtesy of
	Ingo Molnar.

2.	Move non-trivial functions from kernel/rcu/rcu_segcblist.h
	to kernel/rcu/rcu_segcblist.c to avoid excessive inlining
	of large functions.

Additional patches open-coding some of the more trivial functions to follow.

							Thanx, Paul

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

 include/linux/rcu_segcblist.h |  628 ----------------------
 init/Kconfig                  |    3 
 kernel/rcu/Makefile           |    1 
 kernel/rcu/rcu_segcblist.c    |  505 ++++++++++++++++++
 kernel/rcu/rcu_segcblist.h    | 1178 ++++++++++++++++++++++++------------------
 kernel/rcu/srcutiny.c         |    1 
 kernel/rcu/srcutree.c         |    1 
 kernel/rcu/tree.h             |    3 
 8 files changed, 1196 insertions(+), 1124 deletions(-)

             reply	other threads:[~2017-05-02 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02 15:35 Paul E. McKenney [this message]
2017-05-02 15:36 ` [PATCH tip/core/rcu 1/2] srcu: Debloat the <linux/rcu_segcblist.h> header Paul E. McKenney
2017-05-02 15:36 ` [PATCH tip/core/rcu 2/2] rcu: Separately compile large rcu_segcblist functions 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=20170502153542.GA19274@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobby.prani@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --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 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.