From: Peter Zijlstra <peterz@infradead.org>
To: Sherif Fadel <fahmy@vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scheduling co-processors
Date: Mon, 03 Aug 2009 17:59:42 +0200 [thread overview]
Message-ID: <1249315182.7924.142.camel@twins> (raw)
In-Reply-To: <1249312084.5762.17.camel@sherif-laptop>
On Mon, 2009-08-03 at 18:08 +0300, 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?
You'd have to hot-unplug the cpus to stop them from being used.
> If so,
> could you please inform me how one would go about this?
Write code ;-), mind you that running stuff on a cpu without the
scheduler present won't allow you to run regular linux stuff.
> 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.
Seems unlikely to work imho, most of the overhead is remote accesses and
by moving everything to one cpu you'll incur those costs all the time.
next prev parent reply other threads:[~2009-08-03 15:59 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 [this message]
2009-08-03 19:52 ` Bill Davidsen
2009-08-03 20:28 ` Casey Dahlin
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=1249315182.7924.142.camel@twins \
--to=peterz@infradead.org \
--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