On Tue, 20 Feb 2007, Max Krasnyansky wrote: > Ok. Sounds like disabling cache_reaper is a better option for now. Like you > said > it's unlikely that slabs will grow much if that cpu is not heavily used by the > kernel. Running for prolonged times without cache_reaper is no good. What we are talking about here is to disable the cache_reaper during cpu shutdown. The slab cpu shutdown will clean the per cpu caches anyways so we really do not need the slab_reaper running during cpu shutdown. - 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/
- Follow-Ups:
- SLAB cache reaper on isolated cpus
- From: Max Krasnyansky <[email protected]>
- SLAB cache reaper on isolated cpus
- References:
- slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Oleg Nesterov <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Christoph Lameter <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Oleg Nesterov <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Christoph Lameter <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Oleg Nesterov <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Max Krasnyansky <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Christoph Lameter <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Oleg Nesterov <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Max Krasnyansky <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Christoph Lameter <[email protected]>
- Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- From: Max Krasnyansky <[email protected]>
- slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- Prev by Date: Re: 2.6.20-mm2
- Next by Date: Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- Previous by thread: Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
- Next by thread: SLAB cache reaper on isolated cpus
- Index(es):