lkml.org 
[lkml]   [2002]   [Oct]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] patch-slab-split-03-tail

> <<<<<<<
> An object cache's CPU layer contains per-CPU state that must be
> protected either by per-CPU locking or by disabling interrupts. We
> selected per-CPU locking for several reasons:
> [...]
> x Performance. On most modern processors, grabbing an uncontended
> lock is cheaper than modifying the processor interrupt level.
> <<<<<<<<
>
> Which cpus have slow local_irq_disable() implementations? At least for
> my Duron, this doesn't seem to be the case [~ 4 cpu cycles for cli]

Rusty did some tests and found on the intel chips he tested
local_irq_disable was slower. He posted the results to lkml a few weeks
ago.

On ppc64 it varies between chips.

Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:29    [W:0.073 / U:1.368 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site