[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: doubt regarding IO scheduler and credit scheduling in netback
- To: xen-devel@xxxxxxxxxxxxxxxxxxx
- From: Kuriakose Mathew <kmathew123@xxxxxxxxx>
- Date: Sat, 24 Oct 2009 15:31:03 +0530
- Delivery-date: Sat, 24 Oct 2009 03:01:31 -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 :content-type; b=nWmKk7XT37EZ9TGP3erbyrxT+VnF6LvwyASnSgV9uqnHG9YE3QFY568kXJWX5ss0jQ SVzcyMWzGIrIO1sawmiO19E/Kwoz6auloEq+ejxyvyvby3KNyb7N5cyjKdo87ktkrT1X 120NAXsPY8RDz7QArW6O6TQ7pTx3C7lwZAxJQ=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
I ll put my question differently.
I have read that there are different
types of IO schedulers in linux - deadline ,anticipatory, complete fair
queueing (cfq )etc. where cfq is the default. Is it only being used in
the context of disk IO? or the same thing is used for network IO? When does this get called with respect to xen frontend-backend drivers .
Please explain.
On Fri, Oct 23, 2009 at 9:20 AM, Kuriakose Mathew <kmathew123@xxxxxxxxx> wrote:
Just to clarify , hope the above credit scheduling has nothing to do with the cpu credit scheduling at the hypervisor?
On Fri, Oct 23, 2009 at 8:46 AM, Kuriakose Mathew <kmathew123@xxxxxxxxx> wrote:
Hi,
With reference to the netback and netfront model of device
driver in Xen(specifically Xen 3.1.3 and linux 2.6.18.8-- I know it is a bit old but please excuse), I am confused as to where the
network IO scheduler fits in. I have read that there are different
types of IO schedulers in linux - deadline ,anticipatory, complete fair
queueing (cfq )etc. where cfq is the default. Is it only being used in
the context of disk IO? or the same thing is used for network IO?
Also (as a related doubt), in netback code(In netback.c net_tx_action ) , I saw some credit scheduling of the network
interfaces(netif_t *netif) corresponding to guest domains. So whenever
Dom 0 is scheduled ,it does a credit scheduling of the network
interfaces corresponding to different DomUs. The credits will get refreshed when the credit_timeout happens. The next network interface(netif) will be scheduled if the credits for the current netif is exhausted. Is my understanding correct ?
What are the other cases when the next netif is scheduled? (one would obviously be the case when there are no packets to send. Any other case?) When I did some experiments, I found that the bandwidth is fairly divided among all the domains. So there should be some mechasim to ensure this.
In this context where does
the IO scheduler fits in?
Please explain.
Thanks
Kuriakose Mathew
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
