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 0/4] Support accelerated network plugin modules

To: Kieran Mansley <kmansley@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/4] Support accelerated network plugin modules
From: Jambunathan K <jambunathan@xxxxxxxxxx>
Date: Fri, 01 Jun 2007 16:25:53 +0530
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Sanjeev Jorapur <sanjeev@xxxxxxxxxx>
Delivery-date: Fri, 01 Jun 2007 03:57:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1180688663.4111.17.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: <1178618095.4147.32.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <465EF908.6050408@xxxxxxxxxx> <1180688663.4111.17.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.0 (Windows/20070326)
Kieran


>> I have a question regarding the feature set that is proposed here. The
>> intention is to further my own understanding and get some additional
>> insights.
>>
>> Doesn't accelerated network plugins solve the same problem as say a
>> "native" PCI passthroughed driver. Put other way, what can an
>> accelerator do that a passthroughed driver cannot do?
> 
> Functionally they're similar, in that they both enable a guest to get
> direct access to the NIC to deliver higher network performance, but off
> the top of my head:
> 
>  - PCI passthrough would require hardware to support multiple PCI
> devices.  The accelerated plugin approach we've put forward doesn't (but
> would also work fine with devices that virtualise at the PCI layer), and
> so would support a wider range of devices.
> 
>  - You're limited with PCI passthrough to the number of PCI devices your
> NIC can support, which is (for the NICs I've seen) considerably less
> than the number of VIs that other NICs can support.  This will limit the
> number of guests you can provide accelerated network interfaces to.
> 
>  - I'm not sure what the story is for migration with PCI passthrough,
> but with the accelerated plugin approach your network interfaces can
> transparently (as far as the guest's network stack is concerned) move
> from being accelerated to not-accelerated (and vice-versa) depending on
> what hardware is available, and migrate from one type of accelerated
> hardware to another.  
> 
>  - A PCI-passthrough-based network interface might struggle to route
> packets to a virtual machine on the same host.  The accelerated network
> plugin can just fall back to the netfront/netback normal network path to
> get packets to these, or use facilities on the NIC to achieve the same
> if available.
> 
> In summary, it's "passthrough" rather than "PCI passthrough", if that
> makes sense.
> 

My understanding very much tallies with the points you have outlined above.

The patches you have submitted is of interest to us. It is possible that
in the near future we would get around to integrating and exercising
your changes against our own driver.

Jambunathan K.

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

<Prev in Thread] Current Thread [Next in Thread>