Christoph Lameter wrote:
> On Tue, 20 Feb 2007, Max Krasnyansky wrote:
>
>> Suppose I need to isolate a CPU. We already support at the scheduler and
>> irq levels (irq affinity). But I want to go a bit further and avoid
>> doing kernel work on isolated cpus as much as possible. For example I
On Tue, 20 Feb 2007, Max Krasnyansky wrote:
> Suppose I need to isolate a CPU. We already support at the scheduler and
> irq levels (irq affinity). But I want to go a bit further and avoid
> doing kernel work on isolated cpus as much as possible. For example I
> would not want to schedule work
Christoph Lameter wrote:
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
Christoph Lameter wrote:
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
On Tue, 20 Feb 2007, Max Krasnyansky wrote:
Suppose I need to isolate a CPU. We already support at the scheduler and
irq levels (irq affinity). But I want to go a bit further and avoid
doing kernel work on isolated cpus as much as possible. For example I
would not want to schedule work
Christoph Lameter wrote:
On Tue, 20 Feb 2007, Max Krasnyansky wrote:
Suppose I need to isolate a CPU. We already support at the scheduler and
irq levels (irq affinity). But I want to go a bit further and avoid
doing kernel work on isolated cpus as much as possible. For example I
would
6 matches
Mail list logo
