[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020908260916l34a21cai1abf7b2ca7ac93a3@mail.gmail.com>
Date: Wed, 26 Aug 2009 19:16:12 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Christoph Lameter <cl@...ux-foundation.org>,
raz ben yehuda <raziebe@...il.com>,
Maxim Levitsky <maximlevitsky@...il.com>,
Chris Friesen <cfriesen@...tel.com>,
Mike Galbraith <efault@....de>, riel@...hat.com, mingo@...e.hu,
andrew motron <akpm@...ux-foundation.org>,
wiseman@...s.biu.ac.il, lkml <linux-kernel@...r.kernel.org>,
linux-rt-users@...r.kernel.org
Subject: Re: RFC: THE OFFLINE SCHEDULER
Hi Peter,
On Wed, Aug 26, 2009 at 7:03 PM, Peter Zijlstra<peterz@...radead.org> wrote:
> There needs to be some communication between the isolated and non
> isolated part, otherwise what's the point. Even when you'd let it handle
> say a network device as pure firewall, you'd need to configure the
> thing, requiring interaction.
The use case Christoph described was an user-space number cruncher app
that does some network I/O over RDMA IIRC. AFAICT, if he could isolate
a physical CPU for the thing, there would be little or no
communication with the non-isolated part. Yes, the setup sounds weird
but it's a real workload although pretty damn specialized.
On Wed, Aug 26, 2009 at 7:03 PM, Peter Zijlstra<peterz@...radead.org> wrote:
>> > If you think the kernel is too fat and does superfluous things for your
>> > needs, help trim it.
>>
>> Mind boogling nonsense. Please stop fantasizing and trolling.
>
> Oh, to lay down the crack-pipe and sod off.
I guess I'll go for the magic mushrooms then.
Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists