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-users

Re: [Xen-users] io scheduler

To: Gerd Hoffmann <kraxel@xxxxxxx>
Subject: Re: [Xen-users] io scheduler
From: Anand <xen.mails@xxxxxxxxx>
Date: Thu, 19 Jan 2006 20:30:11 +0530
Cc: Xen Users <Xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 19 Jan 2006 15:08:05 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hGYHK4sWbGgmCf0OG1pjMqibCQ7CMHWemmiJzTHJE8mzTdMSyL0yq9zWd/viH+PxDhVFHCDE/EYjW2LHGByAllPrGKmtIVOIaQgRALevFKiZIZ41MWBgLPw0kJeXBOrtILK7EbgWWAx/bK2FA+geJTmMiW43OvyxntXK/NCwmn4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43CF162C.5000800@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <acb757c00601100317y36f100c7n308042ac373273c2@xxxxxxxxxxxxxx> <Pine.LNX.4.44.0601101137320.6446-100000@xxxxxxxxxxxxxxxxxx> <acb757c00601151253o2744d8bpce7dabcac90ec933@xxxxxxxxxxxxxx> <acb757c00601171257i5a76ceadr10957e10891f5661@xxxxxxxxxxxxxx> <acb757c00601171305i58876452p2983ff0acb22d62b@xxxxxxxxxxxxxx> <acb757c00601171311t61a45254r8a6ea77bed5cc422@xxxxxxxxxxxxxx> <43CF162C.5000800@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 1/19/06, Gerd Hoffmann <kraxel@xxxxxxx> wrote:
No, it's in the backend driver, thus you have to replace the dom0
kernel.  No protocol changes, so you can just drop-in the new kernel and
everything should work.

Actually thats what i meant through my post. Anyways i was mixed up with too many things when i posted that so the post could have sounded confusing ;)

With the new dom0 kernel you'll have one kernel thread per virtual block
device.  This helps the I/O scheduler (which uses the PID to decide how
to group/queue requests) to do a better job.  It also allows you to
tweak the priorities using ionice (comes with recent util-linux versions).

Any ways i can actually check and see how this is happening and how to verify if its working properly ? I am working only on a devel box so putting actual load inside domU's is not possible right now.

--

regards,

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