linux-kernel - Re: SCHED

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 8 May 2009 11:10:52 +0200
From:	Henrik Austad <henrik@...tad.us>
To:	GeunSik Lim <leemgs1@...il.com>
Cc:	finarfin@...amos.org, linux-kernel@...r.kernel.org
Subject: Re: SCHED_EDF infos

On Fri, May 08, 2009 at 11:35:58AM +0900, GeunSik Lim wrote:
> Hi Henlik,

Hi Lim,


First off, to all of you, sorry for my last, very poorly formatted email. I 
have now tranceded into the realms of mutt.

> [..]
> I think so.
> How can we approach  EDF implementation like Pfair as a generic solution
> for Multicore in Linux?

I am working on an implementation now, and I hope to be able to release a 
prototype by the end of next week. I think we can continue the discussion 
then based on that.

> > I'm working on SCHED_PFAIR :-) Which is a multicore, ratebased deadline 
> > driven global scheduling policy where I use the PD^2 rules to solve 
> > tie-breaks. In theory, it can reach 100% utilization on all cores 
> > without missing deadlines (but in practice you will only get close to 
> > 100% as it is not perfect).

> > [..]
> > I'd suggest getting the scheduler running first, then look at those
> > problems later. If you spend all your time trying to learn the 
> > scheduler and design in every little feature you need, you'll never 
> > finish in time.

> In fact, I also  don't have perfect know how to solve PI in Multicore.
> [...]
> > deadline inversion will be a problem, in fact, whatever you chooose to 
> > be the 'key' for picking tasks (priority, niceness, deadlines, wind 
> > direction, <whatever>), you can pretty much take that and add a 
> > -inversion after it. :)

No, PI is going to be deadly no matter what you do.

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