[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Question about the ability of credit scheduler to handle I/O and CPU intensive VMs


  • To: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • From: Yuehai Xu <yuehaixu@xxxxxxxxx>
  • Date: Thu, 7 Oct 2010 20:25:12 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, yhxu@xxxxxxxxx
  • Delivery-date: Thu, 07 Oct 2010 17:26:19 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=aqh5idGxDdirMM99s5mXWMMrYFZZqDrlGuPndhue7LNXROX5qDBD7dAtJE/WUb75Jj QjLBNWzY1jlqFbCjP/yyPdzWF7GP+ECpyMkbSd4TBtyHfq+GIrcXozl3w7BHgG8C7lxG TbG+cV3JGqhfnvrGESvmteGRF7MSWHh1KL9Hg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> I originally considered that when a Dom has an I/O event, its VCPU
> would be waken up, in another word, csched_vcpu_wake(struct vcpu *vc)
> should be invoked. However, I find I am definitely wrong. As long as
> there is a CPU intensive program running in a Dom, this Dom should
> never be in a state of "sleep"? In another word, it should never be
> waken up?
>

The trace result from xenalyze confirms that when a VM has a running
CPU intensive program, it never needs to be waken up. So, my question
is, how can I schedule a VM that has I/O event immediately even this
VM is CPU intensive? I think it is impossible to implement it in the
function csched_vcpu_wake.

Also, is it possible to trace the I/O procedure by xenalyze? I notice
even the macro TRC_HVM_IO_READ is defined, I don't find it is used in
anywhere.

Thanks,
Yuehai

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.