All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jambunathan K <jambunathan@netxen.com>
To: Kieran Mansley <kmansley@solarflare.com>
Cc: xen-devel@lists.xensource.com, Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: [PATCH 0/4] Support accelerated network plugin	modules
Date: Fri, 01 Jun 2007 16:25:53 +0530	[thread overview]
Message-ID: <465FFB39.4070409@netxen.com> (raw)
In-Reply-To: <1180688663.4111.17.camel@moonstone.uk.level5networks.com>

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.

      reply	other threads:[~2007-06-01 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08  9:54 [PATCH 0/4] Support accelerated network plugin modules Kieran Mansley
2007-05-08 10:43 ` Keir Fraser
2007-05-09  9:37 ` Herbert Xu
2007-05-09 11:26   ` Muli Ben-Yehuda
2007-05-09 11:59     ` Kieran Mansley
2007-05-31 16:34 ` Jambunathan K
2007-06-01  9:04   ` Kieran Mansley
2007-06-01 10:55     ` Jambunathan K [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465FFB39.4070409@netxen.com \
    --to=jambunathan@netxen.com \
    --cc=kmansley@solarflare.com \
    --cc=sanjeev@netxen.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.