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/
Home Products Support Community News


Re: [Xen-devel] Trying to get HyperSCSI and Xen to work... ;-)

To: Nick Craig-Wood <ncw1@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Trying to get HyperSCSI and Xen to work... ;-)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 09 Oct 2003 17:16:19 +0100
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Oct 2003 17:20:32 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 09 Oct 2003 17:10:44 BST." <20031009161044.GA18298@xxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> On Thu, Oct 09, 2003 at 12:25:15AM +0100, Keir Fraser wrote:
> > A lot of the network control code (e.g., routing of packets) isn't
> > great. We want to rework it at some point in the near future -- adding
> > more flexible packet forwarding, filtering and rewriting. The code has
> > evolved into its current form rather than being cleanly designed :-(
> Are there any plans to add rate limiting of network packets per domain
> (in and out)?  This seemed to be the only feature missing from Xen for
> use in a hostile shared hosting environment.  I read it has a fair
> scheduler for packet traffic which is great.  Being able to put a cap
> on the absolute traffic levels would be even better.

Yes, several people are interested in implementing more versatile I/O
and CPU scheduler. This should see some progress in the near future.

I think ading simple rate-limiting to the current network scheduler
would not be much work.

 -- Keir

This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
Xen-devel mailing list