From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: linux-kernel@vger.kernel.org, Josh Triplett <josh@joshtriplett.org>
Subject: Re: [RFC PATCH v2] tinification: Introduce CONFIG_SRCU to make SRCU optional
Date: Thu, 4 Dec 2014 10:02:10 -0800 [thread overview]
Message-ID: <20141204180210.GS25340@linux.vnet.ibm.com> (raw)
In-Reply-To: <54807FC3.9050305@gmail.com>
On Thu, Dec 04, 2014 at 10:37:39AM -0500, Pranith Kumar wrote:
> On 12/04/2014 01:27 AM, Paul E. McKenney wrote:
> > For the moment, I applied this to -rcu against v3.18-rc6 to get some 0day
> > testing on it.
> >
> > There are conflicts against the tip of my tree, but will worry about
> > that later. I don't have a ready answer on whether or not this needs
> > to be split up -- in the worst case, we would add the SRCU Kconfig
> > parameter, add all the selects, then once they all hit mainline add the
> > Makefile change.
> >
> > We will need stats on how much memory was saved, and a "size kernel/rcu/srcu.o"
> > after a UP/tiny build should do it. Could you please add this to the
> > commit log?
> >
>
> So if we do not select CONFIG_SRCU, srcu.o will not be compiled at all. So we should save about
>
> text data bss dec hex filename
> 2007 0 0 2007 7d7 kernel/rcu/srcu.o
>
> as in size of arch/powerpc/boot/zImage changes from
>
> text data bss dec hex filename
> 831552 64180 23944 919676 e087c arch/powerpc/boot/zImage : before
> 829504 64180 23952 917636 e0084 arch/powerpc/boot/zImage : after
>
> so about ~2000 bytes I guess.
Nice!
Josh, I recall you having a tinified .config somewhere, but don't see it
right off. If you do have one, could you please share it with Pranith?
Not a big deal, just don't want to overstate the savings too much. ;-)
Thanx, Paul
next prev parent reply other threads:[~2014-12-04 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 4:03 [RFC PATCH v2] tinification: Introduce CONFIG_SRCU to make SRCU optional Pranith Kumar
2014-12-04 6:27 ` Paul E. McKenney
2014-12-04 15:37 ` Pranith Kumar
2014-12-04 18:02 ` Paul E. McKenney [this message]
2014-12-04 16:13 ` Josh Triplett
2014-12-04 20:27 ` Pranith Kumar
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=20141204180210.GS25340@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bobby.prani@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.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