[lkml]   [2006]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[patch 0/3] NUMA slab locking fixes
    There were some locking oddities in the NUMA slab allocator which broke cpu
    hotplug. Here is a patchset to correct locking and also fix the
    breakage with cpu hotplug Sonny Rao noticed on POWER5. We hit the bug
    on POWER, but not on other arches because other arches failed to update
    the node cpumasks when a cpu went down.

    Following patches are included in the series:

    1. slab-colour-next fix: Moves the slab colouring index from kmem_cache_t
    to kmem_list3. Per node cache colouring makes sense, and also, we can now
    avoid taking the cachep->spinlock in the alloc patch (cache_grow). Now, alloc
    and free need not take cachep->spinlock and just need to take the respective
    kmem_list3 locks.

    2. slab-locking-irq-optimization: With patch 1, we don't need to disable
    on chip interrupts while taking the cachep->spinlock. (We needed to disable
    interrupts while taking cachep->spinlock earlier because alloc can happen
    from interrupt context, and we had to take the cachep->lock to protect
    color_next -- which is not the case now).

    3. slab-hotplug-fix: Fix the cpu_down and cpu_up slab locking. When the last
    cpu of a node goes down, cpu_down path used to free the shared array_cache,
    alien array_cache and l3, with the kmem_list3 lock held, which resulted in
    badness. This patch fixes the locking not to do that. Now we don't free
    l3 on cpu_down (because there could be a request from other cpus to get
    memory from the node going down, while the last cpu is going down). This
    fixes the problem reported by Sonny Rao.

    2.6.16-rc1mmm4 with the above patches ran successfully overnight on a 4 cpu 2
    node amd tyan box, with 4 dbench processes running all the time and cpus
    offlined and onlined in an infinite loop.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-02-03 21:56    [W:0.039 / U:10.796 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site