* Andi Kleen ([EMAIL PROTECTED]) wrote:
> > On embedded systems, the tradeoff is not the same. The immediate values
> > trade a little bit of system memory (to keep the pointers to the
> > variable and instruction as well as the size of the variable, only used
> > when the variable is updated) in o
> On embedded systems, the tradeoff is not the same. The immediate values
> trade a little bit of system memory (to keep the pointers to the
> variable and instruction as well as the size of the variable, only used
> when the variable is updated) in order to remove cache line hot paths.
Please rem
Should be dropped,
replaced by :
immediate-values-kconfig-embedded.patch
* Mathieu Desnoyers ([EMAIL PROTECTED]) wrote:
> Immediate values provide a way to use dynamic code patching to update
> variables
> sitting within the instruction stream. It saves caches lines normally used by
> static read
* Alexey Dobriyan ([EMAIL PROTECTED]) wrote:
> On Fri, Jul 13, 2007 at 09:24:43PM -0400, Mathieu Desnoyers wrote:
> > Immediate values provide a way to use dynamic code patching to update
> > variables
> > sitting within the instruction stream. It saves caches lines normally used
> > by
> > stati
On Fri, Jul 13, 2007 at 09:24:43PM -0400, Mathieu Desnoyers wrote:
> Immediate values provide a way to use dynamic code patching to update
> variables
> sitting within the instruction stream. It saves caches lines normally used by
> static read mostly variables.
> kernel/Kconfig.immediate | 11
Immediate values provide a way to use dynamic code patching to update variables
sitting within the instruction stream. It saves caches lines normally used by
static read mostly variables.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Adrian Bunk <[EMAIL PROTECTED]>
CC: Andi Kleen <[EMAI
6 matches
Mail list logo
