xen-devel
[Xen-devel] Re: [RFC PATCH 32/33] Add the Xen virtual network device dri
To: |
Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [RFC PATCH 32/33] Add the Xen virtual network device driver. |
From: |
John Haller <jhaller@xxxxxxxxxx> |
Date: |
Tue, 18 Jul 2006 08:25:49 -0500 |
Cc: |
akpm@xxxxxxxx, zach@xxxxxxxxxx, jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, rusty@xxxxxxxxxxxxxxx, hadi@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, ak@xxxxxxx, chrisw@xxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, Christian.Limpach@xxxxxxxxxxxx, arjan@xxxxxxxxxxxxx |
Delivery-date: |
Thu, 20 Jul 2006 05:20:46 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<E1G2pJ3-0003LN-00@xxxxxxxxxxxxxxxxxxxxxxxx> |
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> |
References: |
<E1G2pJ3-0003LN-00@xxxxxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Thunderbird 1.5.0.4 (Windows/20060516) |
Herbert Xu wrote:
jamal <hadi@xxxxxxxxxx> wrote:
I dont think the ifup/ifconfig provide operational status (i.e link
up/down) - or do they? If they can be made to invoke scripts in such
a case then we are set.
In fact, that's a very good reason why this shouldn't be in netfront.
Indeed, it shouldn't be in the guest at all. The reason is that the
guest has no idea whether the physical carrier is present.
It's much better for the host to send the ARP packet on behalf of the
guest since the host knows the carrier status and the guest's MAC
address.
But sending ARPs is not the right thing if the guest is expecting
to use IPv6 networking, in which case unsolicited neighbor
advertisements are the right thing to do. The driver just
doesn't seem to be the right place to do this, as it doesn't/
shouldn't need to know the difference between IPv4/IPv6.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|