lkml.org 
[lkml]   [2007]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
    On Tue, 20 Feb 2007, Max Krasnyansky wrote:

    > I guess I kind of hijacked the thread. The second part of my first email was
    > dropped. Basically I was saying that I'm working on CPU isolation extensions.
    > Where an isolated CPU is not supposed to do much kernel work. In which case
    > you'd want to run slab cache reaper on some other CPU on behalf of the
    > isolated
    > one. Hence the proposal to explicitly pass cpu_id to the reaper. I guess now
    > that you guys fixed the hotplug case it does not help in that scenario.

    A cpu must have a per cpu cache in order to do slab allocations. The
    locking in the slab allocator depends on it.

    If the isolated cpus have no need for slab allocations then you will also
    not need to run the slab_reaper().

    -
    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: 2007-02-20 22:39    [W:2.251 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site