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

[Xen-devel] Re: Accounting in Credit Scheduler

To: ncmike@xxxxxxxxxx
Subject: [Xen-devel] Re: Accounting in Credit Scheduler
From: rahul gundecha <rahoolgundecha@xxxxxxxxxxx>
Date: Mon, 9 Apr 2007 15:40:53 +0100 (BST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 09 Apr 2007 07:39:52 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=I7g2+3gyNtuMKzNx50C7/GbdSRNN+biH9CrD9uFkUkhTzA6D70O3cb9gLr6c/GbioliUdvdsVIQPYHVZBAim/kTSyRPBa4FrgTVuiiaOQVj+DHudkHzzPsOgvv7theiv4Df97rmalI3+BFWq+GJMJe6/7cfPY42yTXKbfuyb2G4=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070409142902.GA2336@xxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
thanks alot Mike for kind reply.

One more curiousity is how often a timer routine is called & how often scheduling code?  It may be configurable interval as well, but then whats default value.
I guess timer is called more frequently & call to scheduling routine is made less frquently and is called from timer itself.

Can I get pointer to some reference where I will get to know how exactly this mechanism works. May be digging through code will be expensive option so I want to avoid it for a moment.

thanks,
-rahul

"Mike D. Day" <ncmike@xxxxxxxxxx> wrote:
On 09/04/07 12:03 +0100, rahul gundecha wrote:
>
> Hi..
> I was going through wiki page of Credit Scheduler which says -
> " The scheduling decision is the common path of the scheduler and is
> therefore designed to be light weight and efficient. No accounting
> takes place in this code path. "
> So where does the accounting process takes place. exctaly by which
> way accounting for CPU, different IO device usage is done. With the
> complex architecture of Xen, how does this accounting process is
> carried out?

The credit scheduler sets up a timer when it is initialized. It does
process accounting during the timer service routine.

The decision to schedule the next vcpu is done on a different code
path, and is optimized to be as fast as possible.

Mike

--
Mike D. Day
IBM LTC
Cell: 919 412-3900
Sametime: ncmike@xxxxxxxxxx AIM: ncmikeday Yahoo: ultra.runner
PGP key: http://www.ncultra.org/ncmike/pubkey.asc




-Rahooooooooooooooool...
exceptions are most common things to happen.....


Here?s a new way to find what you're looking for - Yahoo! Answers
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel