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

Re: [Xen-devel] [PATCH] allow netif frontend to indicate ethernet multic

To: Kieran Mansley <kmansley@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] allow netif frontend to indicate ethernet multicast groups of interest
From: David Edmondson <dme@xxxxxxx>
Date: Thu, 22 Nov 2007 15:40:18 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Nov 2007 07:41:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1195740728.4190.27.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <C36B3C30.18DFC%Keir.Fraser@xxxxxxxxxxxx> <1195740728.4190.27.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 22 Nov 2007, at 2:12pm, Kieran Mansley wrote:
On Thu, 2007-11-22 at 14:01 +0000, Keir Fraser wrote:
How does a frontend detect whether these options are supported by the
backend? What happens across save/restore? Would this be better implemented
by a multicast list in xenstore?

A per-guest-vif list in xenstore would also have the advantage that it
would be easily accessible and usable by the network acceleration
modules, without having to republish the add/remove requests from
netback to any registered accelerators.

The best approach for accelerators would seem to depend somewhat on the hardware implementation. If the frontend plugin is able to deal with the request, there might be no need for the backend plugin to do anything.

Having netfront propagate the request to both the frontend plugin and the backend (which would relay it to the backend plugin) seems straightforward.

Parsing the xenstore entries in more than one place seems like an odd approach, particularly as there would ideally be coordination between the software driver and the accelerator.

dme.
--
David Edmondson, Solaris Engineering, http://dme.org



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