WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] Xen & AoE problem = Ethernet padding

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen & AoE problem = Ethernet padding
From: Marcelo Messa <mrmessa@xxxxxxxxx>
Date: Fri, 25 Jan 2008 00:27:09 -0200
Cc: Marcelo Messa <mrmessa@xxxxxxxxx>
Delivery-date: Mon, 28 Jan 2008 02:32:33 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; bh=v+4/bGmR+53ZABvgCT9DyFqMnXleKnwXHS1YhfgM64o=; b=LvYcL1k59E+VJWV98i5VYCwG52CrD9/hFQTwtvgr3w4eVYPAeXVOtjjXy+VtDm5oGJiI618CXrlgZkNUgm4sxfZU4JzPeQ4A0lJSl3hnOwJMQpPXZicwr3jambW5uNfhB/K2TcoE9zq6WBIubCWv/7mC9vswgm/mpKtsz+KDPzo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=Oi53qAbXpzyymVXGYPFZKbPzbhJN0wCR0tKFirThW6f5b0N6PL19ME9Jw42C0n33Q9WQrMe3N1z+ELD3LtGjCjEVGmrCVQ9eGXnWCvqzftklXH55+G2rSRaDbmhHfImvWS7znQQ9a/hE6Ncno6H4E5uZubXYwii16lSf3JRrnWs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


Hi there,

         This is not a "broadcast", but also, a kind of ping.

I have an entry at http://bugzilla.xensource.com/bugzilla/ show_bug.cgi?id=1140 , and maybe some of you could be interested.

          It follows:
------------------------------------
Hi,

I made some tests about ethernet padding ( an expected behavior from ethernet 10/100 on-wire, that needs at least 60 bytes of data to be able to CRC. NIC chipset has the job of fullfill the packet if it is smaller than this - also called "padding" ) and I notice a behavior that is not expected (at
least for me).


>>> Ethernet Padding Sender  /  Receiver Matrix <<<

      \RECEIVER  | Dom0_vif |FullV_DomU_2|ParaV_DomU_2|SMP_ParaV_DomU_2
SENDER/
Dom0_vif#######|  No (OK)  |  Yes (OK) |  No (NOK) | No (NOK)
FullV_DomU#####|  No (NOK) |  Yes (OK) |  No (NOK) | No (NOK)
ParaV_DomU####|  No (NOK) |  Yes (OK) |  No (NOK) | No (NOK)
SMP_ParaV_DomU|  No (NOK) |  Yes (OK) |  No (NOK) | No (NOK)

My setup is a Centos 5.1 (2.6.18-53.1.4.el5xen) / Xen (3.0.3 or 3.1, as I hear) in a
bridge network configuration.

The results shows that only FullVirtualization do padding, and only when
receives a packet (not when send it).

You could ask "why padding if you dont have a physical transport?". If you are playing with some L2 protocol (like AoE), this behavior do impact.

A direct related problem: it's not possible to export AoE disks from Dom0 and other Paravirtualized guests (AoE blade server verifies if the packet has a minimal size - 60 bytes) to any local VM. I do not known if another layer2 protocols has the same problem, but I think that is a expected feature
that a virtual NIC works as a physical one.

Best Regards
      Marcelo Messa





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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Xen & AoE problem = Ethernet padding, Marcelo Messa <=