From: raz ben yehuda <raziebe@013.net>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: raz ben yehuda <raziebe@013.net>, linux-rt-users@vger.kernel.org
Subject: Re: Subject: PATCH : offline scheduler ( some refer to it as a CPU isolation )
Date: Sun, 19 Apr 2009 13:09:33 +0300 [thread overview]
Message-ID: <1240135773.3395.18.camel@raz> (raw)
In-Reply-To: <c384c5ea0904181823m42a180d7p34d57ad8212ccc54@mail.gmail.com>
On Sun, 2009-04-19 at 03:23 +0200, Leon Woestenberg wrote:
> Raz,
>
> On Sat, Apr 18, 2009 at 8:57 PM, raz ben yehuda <raziebe@013.net> wrote:
> > offsched is a platform aimed to assign a service to an off-lined processor.
> > Motivation is explained in:
> > http://sos-linux.svn.sourceforge.net/viewvc/sos-linux/offsched/trunk/Documentation/OFFSCHED.pdf
>
> I quickly glanced over but could not find a comparison with other methods?
>
>
> Suppose I run /bin/init with a certain CPU affinity (not covering all
> CPUs) and then run my own specific service on the remaining CPUs, how
> would this differ from your approach?
First , not all services are children of init. there are workqueues,
kernel daemons, softirqs and so on. offlet provides hard real time,in
the sense that one can pre-determine how long an operation cost, it is
NMI mode after all. Also, this is why i chose to implement a 1us timer,
because i can do it.
> >From what I quickly gathered, you are running parts of the kernel
> space on the second CPU set, or is that too simple a statement?
I am running **no kernel** on the offloaded processors, but offsched code,
and the rest of the processors run the "kernel".
>
> Looks like a very fresh approach, nice project!
Thank you. i appreciate it.
> Regards,
prev parent reply other threads:[~2009-04-19 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 18:57 Subject: PATCH : offline scheduler ( some refer to it as a CPU isolation ) raz ben yehuda
2009-04-19 1:23 ` Leon Woestenberg
2009-04-19 10:09 ` raz ben yehuda [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1240135773.3395.18.camel@raz \
--to=raziebe@013.net \
--cc=leon.woestenberg@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).