DPDK website maintenance
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: web@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
	 Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-web] [PATCH] Update roadmap for the Broadcom's bnxt PMD
Date: Wed, 1 Mar 2017 13:26:32 -0600	[thread overview]
Message-ID: <CACZ4nhutq2pFCTLw0ATLJe=V4zs3r2u-PR8-u8UPutLm_x6C6w@mail.gmail.com> (raw)
In-Reply-To: <20170227174749.8028-1-ajit.khaparde@broadcom.com>

Please let me know if the list is worth being a part of the roadmap.
Or if it needs any modification.

Thanks
Ajit

On Mon, Feb 27, 2017 at 11:47 AM, Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:

> This updates the roadmap for Broadcom's bnxt PMD for 17.05 release.
> ---
>  dev/roadmap.html | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/dev/roadmap.html b/dev/roadmap.html
> index 9aa701e..bc52cc2 100644
> --- a/dev/roadmap.html
> +++ b/dev/roadmap.html
> @@ -51,6 +51,11 @@
>                 <li>Atomic Rules net/ark Arkville Driver
>                 <li>Xen Netfront Driver
>                 <li>New device types in vhost-user
> +               <li>Add more dev_ops like set_vf_rate_limit,
> set_vf_vlan_filter,
> +               set_vf_rx_mode, udp_tunnel_port_add/del, VLAN filtering and
> +               stripping, stateless tunnel offload, xstats_get/reset,
> +               set_mc_addr_list, mac_addr_set_op and update the HWRM API
> to
> +               version 1.7.1 to Broadcom's bnxt driver.
>         </ul>
>         <h3 id="1708">Version 17.08 (2017 August)</h3>
>         <ul>
> --
> 2.10.1 (Apple Git-78)
>
>

  reply	other threads:[~2017-03-01 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 17:47 Ajit Khaparde
2017-03-01 19:26 ` Ajit Khaparde [this message]
2017-03-01 19:38   ` Thomas Monjalon
2017-03-02  9:39     ` Mcnamara, John
2017-03-02 23:29       ` [dpdk-web] [PATCH v2] " Ajit Khaparde
2017-03-03 14:54         ` Thomas Monjalon

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='CACZ4nhutq2pFCTLw0ATLJe=V4zs3r2u-PR8-u8UPutLm_x6C6w@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=thomas.monjalon@6wind.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).