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


[Xen-devel] [PATCH 0 of 7] Remus: pvops dom0 support

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0 of 7] Remus: pvops dom0 support
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Mon, 03 May 2010 11:53:47 -0700
Delivery-date: Mon, 03 May 2010 12:01:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mercurial-patchbomb/1.5.1+148-ee05131ca51a
The following patch series makes it possible to run Remus on top of
pvops dom0. Specifically, it uses the IFB device (included with newer kernels)
for buffering outbound network traffic, instead of the old 3rd-party IMQ patch.

It also cleans up some bugs in the python rtnetlink bindings, supports
guests with multiple VIFs, and allocates unused IFB/IMQ devices to allow
concurrent protection of multiple guests.

No non-Remus code is touched by these patches. With these patches applied, the
IMQ patch can be dropped from the pvops tree.

Xen-devel mailing list