From mboxrd@z Thu Jan  1 00:00:00 1970
From: Diwaker Gupta <diwaker.lists@gmail.com>
Subject: sedf oversubscription
Date: Mon, 29 Aug 2005 16:49:02 -0700
Message-ID: <891be9410508291649328d6b29@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

I looked around but haven't found a definitive answer to this on the
mailing list archives -- how does SEDF handle oversubscription? I'm
not using weights at all -- just period/slice specifications for each
domain. So what happens if a user tries to give a specification where
sum(period/slice over all domains) > 1?

Looking at the code it seems that SEDF just *assumes* that the
specification will be valid. Is that correct? Does anyone have a
handle on how the scheduler will behave if an invalid spec is given? I
guess I could just try for myself....

--=20
Web/Blog/Gallery: http://floatingsun.net