From: Jambunathan K <jambunathan@netxen.com>
To: xen-devel@lists.xensource.com
Cc: Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: [PATCH 0/4] Support accelerated network plugin modules
Date: Thu, 31 May 2007 22:04:16 +0530 [thread overview]
Message-ID: <465EF908.6050408@netxen.com> (raw)
In-Reply-To: <1178618095.4147.32.camel@moonstone.uk.level5networks.com>
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?
Regards,
Jambunathan K.
Kieran Mansley wrote:
> This series of patches adds support to netfront and netback to allow
> accelerated drivers to plug in and support a fast path for network
> traffic. This is designed to allow use of virtualisable "smart" NICs
> directly from domU, with help/control from dom0. Experiments with
> Solarflare hardware have shown a doubling in network performance when
> using this approach on 10Gbps networks, compared to the traditional
> network path through netfront/netback. i.e. Performance from domU
> approaches that normally seen in dom0.
>
> The patches are as follows:
>
> 1/4: Add xenbus_for_each_[back,front]end functions to iterate each bus
> - this is just a pair of simple helper functions to allow each item on
> the backend/frontend bus to be iterated.
>
> 2/4: Add accel option to vif xend config
> - this allows users to specify which vif interfaces should be
> accelerated, and which plugin module should be used.
>
> 3/4: Frontend net driver acceleration
> - this provides hooks in the netfront driver to allow a plugin module
> to attach and be called at appropriate points.
>
> 4/4: Backend net driver acceleration
> - this provides hooks in the netback driver to allow a plugin module to
> attach and be called at appropriate points.
>
>
> Kieran
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2007-05-31 16:34 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 [this message]
2007-06-01 9:04 ` Kieran Mansley
2007-06-01 10:55 ` Jambunathan K
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=465EF908.6050408@netxen.com \
--to=jambunathan@netxen.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.