[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170506071551.owtodttlhwvjrtzp@gmail.com>
Date: Sat, 6 May 2017 09:15:51 +0200
From: Ingo Molnar <mingo@...nel.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: FYI, tiny-kernel fix for rcu_segcblist separate .c file
* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
> Hello, Ingo,
>
> Just in case you get complaints about kernel size...
>
> In response to Linus's feedback, I did commit 98059b98619d ("rcu:
> Separately compile large rcu_segcblist functions"), which of course
> has the side-effect of bloating Tiny SRCU, which 0day Test Robot
> complains about.
>
> So I have queued commit 7bf7fa5acc92 ("srcu: Apply trivial callback
> lists to shrink Tiny SRCU"), which makes up for the bloating and then some.
>
> I don't believe that this debloating is at all urgent because people
> building kernels for small-memory devices have to do a lot of other
> tweaking, so that applying this additional commit as a patch should
> not be too much incremental pain.
>
> So again, if you get complaints about 98059b98619d bloating tiny
> kernel builds, 7bf7fa5acc92 is the fix.
Ok!
I do agree that it's not urgent: single CPU systems are rapidly becoming the
exception for new hardware designed, even for embedded systems. At this point
I think the educational value of TinyRCU is its main quality.
Thanks,
Ingo
Powered by blists - more mailing lists