All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: "G. Milos" <gm281@hermes.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Scheduling of I/O domains
Date: Wed, 21 Jul 2004 16:25:26 -0600	[thread overview]
Message-ID: <40FEED56.7040109@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0407211914590.2885@hermes-1.csi.cam.ac.uk>

G. Milos wrote:
> 
> To target the unfairness I am developing a modification of BVT (I called 
> it Fair Borrowed Virtual Time [FBVT]). You can enable it by supplying 
> "sched=fbvt" command to Xen at the startup. The scheduler is under 
> development and it needs some tweaking to get the best performance (that 
> is what I am working on at the moment). It would be very helpful if you 
> could email me with the results of your tests for FBVT.


I tried booting xen with "sched=fbvt" in the command line in grub.conf. 
It didn't change the results at all. And why would it? We are not 
dealing with an "I/O bound domain" here, but rather with an "I/O 
domain", two very different things.

It seems to me that this problem doesn't have anything to do with the 
choice of scheduling policy or parameters; It is about when the 
scheduler is called. It appears as though the xen cpu scheduler 
currently only runs when the hardware timer ticks. It does not run when 
an external interrupt happens. So there is a large latency introduced to 
I/O interrupts, and this limits I/O performance. Changing the scheduler 
algorithm won't help this.

The only way to avoid this is to immediately dispatch the I/O domain 
responsible for a given I/O interrupt as soon as that interrupt occurs. 
This means giving I/O domains with pending interrupts scheduling 
priority over any "regular" domains. Just as in a "normal" operating 
system, interrupt service routines must complete before any user 
processes are executed. Otherwise, latencies are introduced that kill 
I/O performance.

Rob Gardner



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

  reply	other threads:[~2004-07-21 22:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 17:21 Scheduling of I/O domains Rob Gardner
2004-07-21 18:54 ` G. Milos
2004-07-21 22:25   ` Rob Gardner [this message]
2004-07-22  0:53     ` Keir Fraser
2004-07-30 13:32       ` Rolf Neugebauer
2004-07-30 14:48         ` G. Milos
2004-07-30 15:23         ` G. Milos
2004-08-05 22:21         ` Rob Gardner
2004-08-06  9:25           ` G. Milos
2004-08-06 21:05             ` Rob Gardner
2004-08-23 17:51               ` Ian Pratt
2004-08-02 11:48 ` G. Milos
  -- strict thread matches above, loose matches on Subject: below --
2004-07-22  0:33 Neugebauer, Rolf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40FEED56.7040109@hp.com \
    --to=rob.gardner@hp.com \
    --cc=gm281@hermes.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.