Re: [patch 08/10] SLUB: Optional fast path using cmpxchg_local

On Sun, 28 Oct 2007, Pekka J Enberg wrote:

> Can you please write a comment of the locking rules when cmpxchg_local() 
> is used? Looks as if we could push that local_irq_save() to slub_lock() 
> and local_irq_restore() to slub_unlock() and deal with the unused flags 
> variable for the non-CONFIG_FAST_CMPXCHG_LOCAL case with a macro, no?

Hmmmm... Maybe .. The locking rules are not changed at all by this patch. 
The cmpxchg_local is only used for the per cpu object list. The per cpu 
slabs are frozen.

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

---

• References:
  • [patch 00/10] SLUB: SMP regression tests on Dual Xeon E5345 (8p) and new performance patches
    • From: Christoph Lameter <[email protected]>
  • [patch 08/10] SLUB: Optional fast path using cmpxchg_local
    • From: Christoph Lameter <[email protected]>
  • Re: [patch 08/10] SLUB: Optional fast path using cmpxchg_local
    • From: Pekka J Enberg <[email protected]>

• Prev by Date: [PATCH] Silence radeon_pm warning
• Next by Date: Re: [patch 09/10] SLUB: Do our own locking via slab_lock and slab_unlock.
• Previous by thread: Re: [patch 08/10] SLUB: Optional fast path using cmpxchg_local
• Next by thread: Re: [patch 08/10] SLUB: Optional fast path using cmpxchg_local
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]