[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070917135517.2436c575.randy.dunlap@oracle.com>
Date: Mon, 17 Sep 2007 13:55:17 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
Adrian Bunk <bunk@...sta.de>, Andi Kleen <andi@...stfloor.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [patch 2/7] Immediate Values - Kconfig menu in EMBEDDED
On Mon, 17 Sep 2007 14:42:26 -0400 Mathieu Desnoyers wrote:
> init/Kconfig | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> Index: linux-2.6-lttng/init/Kconfig
> ===================================================================
> --- linux-2.6-lttng.orig/init/Kconfig 2007-09-04 11:53:59.000000000 -0400
> +++ linux-2.6-lttng/init/Kconfig 2007-09-04 12:12:03.000000000 -0400
> @@ -407,6 +407,17 @@ config CC_OPTIMIZE_FOR_SIZE
> config SYSCTL
> bool
>
> +config IMMEDIATE
> + default y if !DISABLE_IMMEDIATE
> + depends on X86_32 || PPC || PPC64
> + bool
> + help
> + Immediate values are used as read mostly variables that are rarely
read-mostly
> + updated. They use code patching to modify the values inscribed in the
> + instruction stream. It provides a way to save precious cache lines
They .... (then) It ...
so choose one of the other. I think I prefer "They".
> + that would otherwise have to be used by these variables. Can be
> + disabled through the EMBEDDED menu.
> +
> menuconfig EMBEDDED
> bool "Configure standard kernel features (for small systems)"
> help
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists