linux-kernel - RE: scheduling co-processors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <000301ca14ee$401f8560$c05e9020$@edu>
Date:	Tue, 4 Aug 2009 13:28:00 +0300
From:	"Sherif F. Fahmy" <fahmy@...edu>
To:	"'Casey Dahlin'" <cdahlin@...hat.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: scheduling co-processors

> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org [mailto:linux-kernel-
> owner@...r.kernel.org] On Behalf Of Casey Dahlin
> Sent: Monday, August 03, 2009 11:28 PM
> To: Sherif Fadel
> Cc: linux-kernel@...r.kernel.org
> Subject: Re: scheduling co-processors
> 
> 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.

Thanks for the info. I think that this will do perfectly.

> 
> --CJD
> --
> 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/

--
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/