[lkml]   [2007]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
    On 02/20, Christoph Lameter wrote:
    > On Tue, 20 Feb 2007, Max Krasnyansky wrote:
    > > > > Well seems that we have a set of unresolved issues with workqueues and cpu
    > > > > hotplug.
    > >
    > > How about storing 'cpu' explicitly in the work queue instead of relying on the
    > > smp_processor_id() and friends ? That way there is no ambiguity when
    > > threads/timers get
    > > moved around.
    > The slab functionality is designed to work on the processor with the
    > queue. These tricks will only cause more trouble in the future. The
    > cache_reaper needs to be either disabled or run on the right processor. It
    > should never run on the wrong processor.

    I personally agree. Besides, cache_reaper is not alone. Note the comment
    in debug_smp_processor_id() about cpu-bound processes. The slab does correct
    thing right now, stops the timer on CPU_DEAD. Other problems imho should be
    solved by fixing cpu-hotplug. Gautham and Srivatsa are working on that.


    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: 2007-02-20 21:09    [W:0.020 / U:15.564 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site