From: David Howells <dhowells@redhat.com>
To: paulmck@linux.vnet.ibm.com
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, niv@us.ibm.com, dvhltc@us.ibm.com,
lethal@linux-sh.org, kernel@wantstofly.org, matthew@wil.cx
Subject: Re: [PATCH] v4 RCU: the bloatwatch edition
Date: Mon, 22 Jun 2009 17:15:29 +0100 [thread overview]
Message-ID: <4851.1245687329@redhat.com> (raw)
In-Reply-To: <20090622160753.GE6754@linux.vnet.ibm.com>
Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Of course, I well remember programming systems with 4K of core memory
> back in the 1970s, and therefore feel a bit guilty about sticking deep
> embedded platforms with the increase in memory footprint represented
> by Hierarchical RCU compared to Classic RCU. And Bloatwatch RCU is much
> smaller and easier to understand/maintain than is Classic RCU.
Both Fujitsu and Panasonic really want to keep the kernel size down.
Squeezing a kernel into a megabyte or less of flash is one of the main aims,
and anything that saves nearly 1K is not to be sneered at.
David
next prev parent reply other threads:[~2009-06-22 16:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 16:34 [PATCH] v4 RCU: the bloatwatch edition Paul E. McKenney
2009-05-05 21:18 ` David Howells
2009-05-06 12:09 ` Ingo Molnar
2009-05-06 18:24 ` Andrew Morton
2009-05-06 19:02 ` Paul E. McKenney
2009-05-06 19:19 ` Andrew Morton
2009-05-06 20:20 ` Paul E. McKenney
2009-05-06 22:22 ` David Howells
2009-05-06 22:51 ` Paul E. McKenney
2009-06-22 11:43 ` David Howells
2009-06-22 12:49 ` Ingo Molnar
2009-06-22 15:29 ` Andrew Morton
2009-06-22 16:07 ` Paul E. McKenney
2009-06-22 16:15 ` David Howells [this message]
2009-06-22 18:09 ` Paul E. McKenney
2009-06-22 16:30 ` Darren Hart
2009-06-22 17:08 ` Paul E. McKenney
2009-06-23 9:48 ` Ingo Molnar
2009-06-23 12:59 ` 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=4851.1245687329@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dvhltc@us.ibm.com \
--cc=kernel@wantstofly.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
/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