DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Allain Legacy <allain.legacy@windriver.com>
Cc: web@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-web] [PATCH] add AVP to supported NIC list
Date: Thu, 06 Apr 2017 23:37:22 +0200	[thread overview]
Message-ID: <1893851.kb8KertNQD@xps13> (raw)
In-Reply-To: <20170330121901.73795-1-allain.legacy@windriver.com>

2017-03-30 08:19, Allain Legacy:
> Adds the Wind River AVP device to the list of supported NICs for the 17.05
> release.
> 
> Signed-off-by: Allain Legacy <allain.legacy@windriver.com>
> ---
>  doc/nics.html | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/nics.html b/doc/nics.html
> index f3eff47..a0fdbcf 100644
> --- a/doc/nics.html
> +++ b/doc/nics.html
> @@ -97,6 +97,10 @@
>  				<li><a href="/doc/guides/nics/vmxnet3.html">vmxnet3</a> (VMware ESXi)</li>
>  				<li><a href="/doc/guides/xen/pkt_switch.html#xen-pmd-frontend-prerequisites">xenvirt</a> (Xen)</li>
>  			</ul>
> +  			<h3>Wind River</h3>
> +			<ul>
> +				<li><a href="/doc/guides/nics/avp.html">avp</a> (Accelerated Virtual Port)</li>
> +			</ul>
>  			<h3>Others</h3>
>  			<ul>
>  				<li><a href="/browse/dpdk/tree/drivers/net/af_packet">af_packet</a> (Linux AF_PACKET socket)</li>
> 

Added in the Paravirtualization section:

                        <h3>Paravirtualization</h3>
                        <ul>
+                               <li><a href="/doc/guides/nics/avp.html">avp</a> (Wind River Accelerated Virtual Port)</li>
                                <li><a href="/doc/guides/nics/virtio.html">virtio-net</a> (QEMU)</li>

      reply	other threads:[~2017-04-06 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 12:19 Allain Legacy
2017-04-06 21:37 ` Thomas Monjalon [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=1893851.kb8KertNQD@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=allain.legacy@windriver.com \
    --cc=ferruh.yigit@intel.com \
    --cc=web@dpdk.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).