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-users] announcement: intelligent network switching between xen

To: echo@xxxxxxxxxxxx
Subject: Re: [Xen-users] announcement: intelligent network switching between xen domains
From: Radu Rendec <radu.rendec@xxxxxxx>
Date: Mon, 06 Jul 2009 13:13:36 +0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 06 Jul 2009 03:14:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1246816398.5517.222.camel@xxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1246713095.2728.20.camel@xxxxxxxxxxx> <1246816398.5517.222.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2009-07-06 at 01:53 +0800, Tim Post wrote:
> A look at the userspace code alone tells me that you have a very firm
> grasp on what you're doing.
> You posted this to (AFAICT) xen-users only, why not xen-devel? 


Thanks for the reply :) We didn't post to xen-devel because we thought
the project were interesting for xen deployments rather than xen
internals and development. But I'll give it a try anyway. Do you think
the original message we posted on xen-users is well suited for xen-devel
(in exactly the same form)?

> Also, what is the latest xen-0 kernel that you are working with? Indeed,
> the project site does need some updating.

Our current development is on 2.6.29, but we also maintain 3 other

Since we only add a hook in the netdevice rx stack (and everything else
is in our own module), we expect it to apply and work on most kernel

We have mostly relied on fedora (and they removed dom0 support in their
kernel starting with FC9), so the latest xen patched kernel that we
actually tested is 2.6.21.

> Most users brave enough to venture beyond 2.6.18-8 are going to need
> solid instructions, or (better) a pre patched xen + lisa kernel to
> download and build. You won't find many FC8 users here. 

Thanks for the tip. The site definitely needs updating and better

> Do you have a developers list? I'm going to try your patches against
> Jaremy's latest tree, I'm counting on breakage but it should not be
> difficult to fix .. net/ is a very shifty place :)

Yes, we do: http://lisa.ines.ro/mailman/listinfo/lisa-devel
It looks like you know your way around kernels and git. Perhaps the
easiest way to do it is to clone our git tree and try to rebase our
branch on top of whatever xen branch you are testing against.

> I'm working on trying it against a xen patched 2.6.25 kernel now. 

I hope you are not using either of the Centos rpms that we announced or
the FC8 2.6.25 rpms you found on our site. The patch in the 2.6.18
centos .src.rpm most probably won't apply (since most skb members
changed from pointers to offsets between 2.6.18 and 2.6.25). The patch
in the 2.6.25 tree is an ancient version of lisa and I'm not even sure
if it contains the xen tcp sum offload adjustments.

So, if pulling directly from our git tree, keep in mind that only the
2.6.29, 2.6.25 and 2.6.18 branches are up-to-date. We plan to backport
on 2.6.21, but the branch is not yet complete.

Should you have any more questions or need further instructions on
deploying lisa, please feel free to ask directly.


Radu Rendec

Xen-users mailing list