[Xen-devel] Xen/AoE skb frag array incompatibility

[Tracy R Reed <treed@xxxxxxxxxxxxxxx>]

Greetings, Xen developers!

I have been using AoE with Xen to great effect and I am very pleased 
with how the whole system has worked out. The two technologies really 
complement each other. I consider it the ultimate setup. Aside from the 
network switch (eventually to be remedied) my serving infrastructure has 
zero single points of failure.
However, this virtualization paradise has a flaw: There seems to be some 
sort of incompatibility in the way AoE uses the skb frag array in the 
latest version of AoE (6-40) and in the way Xen uses it. This causes new 
AoE block devices to fail to be accessible among potentially other problems.
Is anyone aware of this problem? It is not clear to me if it is a 
problem with Xen or if the fault lies in AoE. I have looked into it a 
bit but my kernel hacking talents are rather meager. Attached is a 
recent email from the AoE list discussing it. If you have any 
suggestions for the AoE folks they can be reached over at 
aoetools-discuss@xxxxxxxxxxxxxxxxxxxxx
--
Tracy R Reed                  http://ultraviolet.org
A: Because we read from top to bottom, left to right
Q: Why should I start my reply below the quoted text

--- Begin Message ---

To:	treed@xxxxxxxxxxxxxxx, ecashin@xxxxxxxxxx
Subject:	Re: [Aoetools-discuss] Unable to open dev /dev/etherd/e1.6:
From:	Sam Hopkins <sah@xxxxxxxxxx>
Date:	Thu, 7 Dec 2006 10:29:25 -0500
Cc:	aoetools-discuss@xxxxxxxxxxxxxxxxxxxxx
Delivered-to:	treed@xxxxxxxxxxxxxxx
In-reply-to:	<4577E48C.7000907@xxxxxxxxxxxxxxx>

> Ed L. Cashin wrote:
>> That sounds similar to the problem that Sam and Adi Kriegisch were
>> recently discussing.  It looked like an incompatibility between our
>> use of "zero-copy writes" and the network layer in his Xen kernels.
>> 
>> Adi Kriegisch said that version aoe6-23 worked for him.
> 
> Hmm...I tried to compile the aoe6-23 version and ran into the old error:
> 
> /root/aoe6-23/linux/drivers/block/aoe/aoenet.c:142: error: too many
> arguments to function `skb_linearize'
> 
> which I can easily fix...then I am reminded that with the aoe driver in
> the stock 2.6.16 kernel I would get the error "Can't schedule work for
> e1.1, it's already on! (This really shouldn't happen)" but it seems that
> is the very old version 14. Hopefully if I just fix the skb_linearize
> arguments in aoe6-23 it will work acceptably. I just hate being the only
>    one running a unique version of the driver.

It would be great if someone close to the Xen community would engage
them about our use of the skb frag array to figure out why this is
happening, since it's a problem that seems to be unique to that
environment.  It is a detriment to aoe that one must hack on old
drivers with missing features to overcome a bug that's already been
identified.

We're not going to maintain an aoe6-23 driver for Xen folks to
workaround a bug.  Fix the bug!

Cheers,

Sam

--- End Message ---

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