linux-kernel - Re: [RFC][PATCH 0/8] Use EDF to throttle RT task groups

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] [day] [month] [year] [list]

Date:	Wed, 15 Jul 2009 16:25:51 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Fabio Checconi <fchecconi@...il.com>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	Gregory Haskins <ghaskins@...ell.com>
Subject: Re: [RFC][PATCH 0/8] Use EDF to throttle RT task groups

On Wed, 2009-07-15 at 14:08 +0200, Fabio Checconi wrote:
> 
> > I might have to re-read that mim-concurrency G-EDF paper again, but I
> > failed to spot the bin-packing issue.
> > 

> In the paper you cited, the Conclusion section lists the support for
> dynamic systems and for joining/leaving of tasks as a future work; I
> think that handling (de-)fragmentation and allocation of cpu bandwidth
> when tasks and groups are created/destroyed might be quite complex from
> within the kernel.

Hmm, right, so I was thinking that we could simply create int(w_i) full
cpu and 1 frac(w_i) server tasks and let the single level G-EDF sort it
out.

It looks to me that by only scheduling the leafs of the hierarchy you
side-step a lot of issues, but then maybe it generates other issues :-)

> I'd prefer to have the mechanims enforcing the bandwidth allocation
> inside the kernel, and, eventually, an interface allowing the userspace
> to specify nontrivial allocation schemes, like the one in the paper.

Right.

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