WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Credit scheduler and latencies

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Credit scheduler and latencies
From: Milan Holzäpfel <listen@xxxxxxxx>
Date: Thu, 14 Dec 2006 18:48:51 +0100
Delivery-date: Thu, 14 Dec 2006 09:48:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061214182443.56278d85.listen@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: mjh.name
References: <20061214182443.56278d85.listen@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 14 Dec 2006 18:24:43 +0100
Milan Holzäpfel <listen@xxxxxxxx> wrote:

> As it seems, a domain/VCPU can in some cases use more than it's fair
> share of PCPU and still interrupt other VCPUs if it only sleeps
> frequently enough.
>
> If a domain/VCPU spins for a long enough amount of time, it does indeed
> not interrupt other VCPUs anymore, with direct effects upon the latency
> I measured.

Thinking about it once again, the problem I'm having with this
behaviour is that a domain can't do I/O with low latency (which
possibly wouldn't require much CPU time by itself) as soon as it starts
consuming lots of CPU time, e.g. because an archiving process has just
started.

Maybe it would be better to always interrupt the currently running
domain for a limited amount of time when another domain receives I/O?

Yet, I think I would still need a smaller scheduler quantum...

Regards,
Milan

Attachment: pgpAU1l3oaVxH.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>