[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020908260806pb85ee72r7b7e32a07b921b59@mail.gmail.com>
Date: Wed, 26 Aug 2009 18:06:21 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: raz ben yehuda <raziebe@...il.com>
Cc: Maxim Levitsky <maximlevitsky@...il.com>,
Christoph Lameter <cl@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
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
On Wed, Aug 26, 2009 at 5:54 PM, raz ben yehuda<raziebe@...il.com> wrote:
>> I have always been fascinated by the idea of controlling another cpu
>> from the main CPU.
>>
>> Usually these cpus are custom, run proprietary software, and have no
>> datasheet on their I/O interfaces.
>>
>> But, being able to turn an ordinary CPU into something like that seems
>> to be very nice.
>>
>> For example, It might help with profiling. Think about a program that
>> can run uninterrupted how much it wants.
>>
>> I might even be better, if the dedicated CPU would use a predefined
>> reserved memory range (I wish there was a way to actually lock it to
>> that range)
>>
>> On the other hand, I could see this as a jump platform for more
>> proprietary code, something like that: we use linux in out server
>> platform, but out "insert buzzword here" network stack pro+ can handle
>> 100% more load that linux does, and it runs on a dedicated core....
>>
>> In the other words, we might see 'firmwares' that take an entire cpu for
>> their usage.
>
> This is exactly what offsched (sos) is. you got it. SOS was partly inspired by the notion of a GPU.
So where are the patches? The URL in the original post returns 404...
--
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