From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: linux-kernel@vger.kernel.org, josh@joshtriplett.org
Subject: Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional
Date: Fri, 12 May 2017 11:45:36 -0700 [thread overview]
Message-ID: <20170512184536.GA10144@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170512184155.GA9482@linux.vnet.ibm.com>
On Fri, May 12, 2017 at 11:41:55AM -0700, Paul E. McKenney wrote:
> On Fri, Apr 28, 2017 at 05:10:40PM -0700, Paul E. McKenney wrote:
> > On Fri, Apr 28, 2017 at 05:51:15PM -0400, Nicolas Pitre wrote:
> > > On Fri, 28 Apr 2017, Paul E. McKenney wrote:
> > >
> > > > Hello, Nicolas!
> > > >
> > > > Saw the TTY write up LWN and figured I should send this your way.
> > > > It should be worth about 2K compared to current -next, which gave
> > > > up the 2K compared to v4.10. So really getting things back to where
> > > > they were.
> > > >
> > > > My current plan is to push this into v4.13.
> > >
> > > Excellent!
> > >
> > > If every maintainer finds a way to (optionally) reduce the size of the
> > > code they maintain by 2K then we'll get a much smaller kernel pretty
> > > soon.
> >
> > I would feel better if it wasn't me who had added the 2K, but then
> > again, I do look forward to seeing a negative-sized kernel! ;-)
>
> And I am getting a lot of offlist pressure to remove both Tiny RCU and
> Tiny SRCU. I am pushing back, but I might or might not prevail. In case
> my pushback gets pushed back, do you have a -tiny tree or some such where
> the code could go?
And adding Josh Triplett on CC, who I should have CCed to start with.
Thanx, Paul
next prev parent reply other threads:[~2017-05-12 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 21:15 [PATCH RFC tip/core/rcu] Make SRCU be once again optional Paul E. McKenney
2017-04-28 21:51 ` Nicolas Pitre
2017-04-29 0:10 ` Paul E. McKenney
2017-05-12 18:41 ` Paul E. McKenney
2017-05-12 18:45 ` Paul E. McKenney [this message]
2017-05-12 18:59 ` Nicolas Pitre
2017-05-12 19:10 ` Paul E. McKenney
2017-06-03 3:59 ` Paul E. McKenney
2017-06-03 5:18 ` Nicolas Pitre
2017-06-03 20:36 ` Paul E. McKenney
2018-01-16 21:02 ` Arnd Bergmann
2018-01-16 21:10 ` Arnd Bergmann
2018-01-16 22:34 ` Paul E. McKenney
2018-01-16 22:55 ` Arnd Bergmann
2018-01-16 23:03 ` Arnd Bergmann
2018-01-16 23:57 ` Paul E. McKenney
2018-01-17 10:29 ` Arnd Bergmann
2018-01-17 16:32 ` Josh Triplett
2018-01-17 17:10 ` Arnd Bergmann
2018-01-17 16:47 ` 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=20170512184536.GA10144@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.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