|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
Re: [Xen-devel] [PATCH] allow netif frontend to indicate ethernet	multic
 
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?
 -- Keir
On 22/11/07 11:38, "David Edmondson" <dme@xxxxxxx> wrote:
> # HG changeset patch
> # User David Edmondson <dme@xxxxxxx>
> # Date 1195652069 28800
> # Node ID 30a7087e908701deb125f55a004c5841dc6c2165
> # Parent  ba69fe2dce91cd7ef633b4b21706344f6be1a6de
> Allow multicast address add/remove requests to be passed from the
> frontend
> to the backend.
> 
> Signed-off-by: David Edmondson <dme@xxxxxxx>
> 
> diff --git a/xen/include/public/io/netif.h b/xen/include/public/io/
> netif.h
> --- a/xen/include/public/io/netif.h
> +++ b/xen/include/public/io/netif.h
> @@ -75,9 +75,11 @@ typedef struct netif_tx_request netif_tx
>   typedef struct netif_tx_request netif_tx_request_t;
> 
>   /* Types of netif_extra_info descriptors. */
> -#define XEN_NETIF_EXTRA_TYPE_NONE  (0)  /* Never used - invalid */
> -#define XEN_NETIF_EXTRA_TYPE_GSO   (1)  /* u.gso */
> -#define XEN_NETIF_EXTRA_TYPE_MAX   (2)
> +#define XEN_NETIF_EXTRA_TYPE_NONE      (0)  /* Never used - invalid */
> +#define XEN_NETIF_EXTRA_TYPE_GSO       (1)  /* u.gso */
> +#define XEN_NETIF_EXTRA_TYPE_MCAST_ADD (2)  /* u.mcast */
> +#define XEN_NETIF_EXTRA_TYPE_MCAST_DEL (3)  /* u.mcast */
> +#define XEN_NETIF_EXTRA_TYPE_MAX       (4)
> 
>   /* netif_extra_info flags. */
>   #define _XEN_NETIF_EXTRA_FLAG_MORE (0)
> @@ -118,9 +120,15 @@ struct netif_extra_info {
>               uint16_t features; /* XEN_NETIF_GSO_FEAT_* */
>           } gso;
> 
> +        struct {
> +            uint8_t addr[6]; /* Address to add/remove. */
> +        } mcast;
> +
>           uint16_t pad[3];
>       } u;
>   };
> +
> +typedef struct netif_extra_info netif_extra_info_t;
> 
>   struct netif_tx_response {
>       uint16_t id;
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 |   
 
 | 
    | 
  
  
    |   | 
    |