From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: "Mody, Rasesh" <Rasesh.Mody@cavium.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Shaikh, Shahed" <Shahed.Shaikh@cavium.com>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] [PATCH 5/7] doc: list NPAR as supported feature in qede
Date: Sat, 5 Aug 2017 05:56:23 +0000 [thread overview]
Message-ID: <BLUPR0701MB739C9F7F85376453E9C69C29FB70@BLUPR0701MB739.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1500891548-21896-5-git-send-email-rasesh.mody@cavium.com>
> From: Rasesh Mody [mailto:rasesh.mody@cavium.com]
> Sent: Monday, July 24, 2017 3:19 AM
>
> From: Shahed Shaikh <Shahed.Shaikh@cavium.com>
>
> Existing qede PMD code already supports NPAR feature.
> So adding this in "Supported Features" section after testing it with latest
> DPDK.
>
> Also, add myself to the list of maintainers of qede PMD
Acked-by: Rasesh Mody <rasesh.mody@cavium.com>
>
> Signed-off-by: Shahed Shaikh <Shahed.Shaikh@cavium.com>
> ---
> MAINTAINERS | 1 +
> doc/guides/nics/qede.rst | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index dc52760..fc26870 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -423,6 +423,7 @@ F: doc/guides/nics/features/bnx2x*.ini
> QLogic qede PMD
> M: Rasesh Mody <rasesh.mody@cavium.com>
> M: Harish Patil <harish.patil@cavium.com>
> +M: Shahed Shaikh <shahed.shaikh@cavium.com>
> F: drivers/net/qede/
> F: doc/guides/nics/qede.rst
> F: doc/guides/nics/features/qede*.ini
> diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst index
> afe2df8..09a10be 100644
> --- a/doc/guides/nics/qede.rst
> +++ b/doc/guides/nics/qede.rst
> @@ -62,13 +62,13 @@ Supported Features
> - VXLAN tunneling offload
> - N-tuple filter and flow director (limited support)
> - LRO/TSO
> +- NPAR (NIC Partitioning)
>
> Non-supported Features
> ----------------------
>
> - SR-IOV PF
> - GENEVE and NVGRE Tunneling offloads
> -- NPAR
>
> Supported QLogic Adapters
> -------------------------
> --
> 1.7.10.3
next prev parent reply other threads:[~2017-08-05 5:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 10:19 [dpdk-dev] [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 2/7] net/qede: fix incorrect queue id for 100G Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 3/7] net/qede/base: fix for adapter specific stats Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 4/7] net/qede: fix inner L3/L4 chksum offload for tunnel frames Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 5/7] doc: list NPAR as supported feature in qede Rasesh Mody
2017-07-28 15:56 ` Mcnamara, John
2017-08-05 5:56 ` Mody, Rasesh [this message]
2017-08-06 10:43 ` Thomas Monjalon
2017-07-24 10:19 ` [dpdk-dev] [PATCH 6/7] net/qede: fix chip details print Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 7/7] net/qede: update PMD version 2.5.2.1 Rasesh Mody
2017-07-31 17:53 ` [dpdk-dev] [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit Ferruh Yigit
2017-08-05 5:59 ` Mody, Rasesh
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=BLUPR0701MB739C9F7F85376453E9C69C29FB70@BLUPR0701MB739.namprd07.prod.outlook.com \
--to=rasesh.mody@cavium.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=Shahed.Shaikh@cavium.com \
--cc=dev@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).