From: Casey Dahlin <cdahlin@redhat.com>
To: Sherif Fadel <fahmy@vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scheduling co-processors
Date: Mon, 03 Aug 2009 16:28:08 -0400 [thread overview]
Message-ID: <4A774858.6080106@redhat.com> (raw)
In-Reply-To: <1249312084.5762.17.camel@sherif-laptop>
On 08/03/2009 11:08 AM, Sherif Fadel wrote:
> Hi,
>
> I have a dual-core system on which I would like to treat one processor
> as a scheduling co-processor. I have already implemented some custom
> scheduling policies and tested them with SMP disabled, I would not like
> to see if it is possible to have the scheduling algorithm running on one
> core and the scheduled tasks running on another.
>
> I do not know if I can somehow use cpus_allowed to restrict the kernel
> to one core and the running tasks to another. Is this possible? If so,
> could you please inform me how one would go about this?
>
> In case you are wondering why I would need this, I am writing a bunch of
> high-overhead distributed scheduling algorithms and I want to mitigate
> their overhead in this way.
>
> Thanks.
>
The design I would have for this would be to have a kthread that does whatever busy work your scheduler has as a separate process. You could then replace the existing scheduler with a sort of "schedulerlet" that would simply schedule according to directions queued up for it by the kthread task. From there cpu affinity should get you the "dedicated scheduler processor" you want.
I can't even begin to envision the scheduling algorithm that would be able to operate this way, but I have to assume that if it makes sense for your scheduler to run on another CPU then it must be able to fit into this pattern.
--CJD
next prev parent reply other threads:[~2009-08-03 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 15:08 scheduling co-processors Sherif Fadel
2009-08-03 15:59 ` Peter Zijlstra
2009-08-03 19:52 ` Bill Davidsen
2009-08-03 20:28 ` Casey Dahlin [this message]
2009-08-04 10:28 ` Sherif F. Fahmy
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=4A774858.6080106@redhat.com \
--to=cdahlin@redhat.com \
--cc=fahmy@vt.edu \
--cc=linux-kernel@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