From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
jingjing.wu@intel.com, helin.zhang@intel.com
Cc: jianbo.liu@linaro.org, chaozhu@linux.vnet.ibm.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v8 2/3] net/i40e: configurable PTYPE mapping
Date: Wed, 12 Apr 2017 09:36:42 +0100 [thread overview]
Message-ID: <dc289d69-f612-ede5-434f-e8fc816ad080@intel.com> (raw)
In-Reply-To: <20170407032505.61691-3-qi.z.zhang@intel.com>
On 4/7/2017 4:25 AM, Qi Zhang wrote:
> The patch adds 4 APIs to support configurable
> PTYPE mapping for i40e device.
> rte_pmd_i40e_ptype_mapping_get.
> rte_pmd_i40e_ptype_mapping_replace.
> rte_pmd_i40e_ptype_mapping_reset.
> rte_pmd_i40e_ptype_mapping_update.
> The mapping from hardware defined packet type to software defined packet
> type can be updated/reset/read out with these APIs.
> Also a software ptype with the most significent bit set will be regarded
> as a user defined ptype (RTE_PMD_I40E_PTYPE_USER_DEFINE_MASK) so
> application can use it to defined its own PTYPE naming system.
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
>
> v5:
>
> - Rebase to dpdk-next-net
>
> v4:
>
> - Add comment to explain the "user defined" ptype.
>
> v2:
>
> - Rename APIs to rte_pmd_i40e_ptype_mapping_xxx
>
> - Add missing API declaration in rte_pmd_i40e_version.map
>
> - Add missing PTYPE in check_invalid_pkt_type
>
> - Fix couple typo error
>
> drivers/net/i40e/i40e_ethdev.c | 229 ++++++++++++++++++++++++++++++
Hi Qi,
These functions now needs to be moved to "rte_pmd_i40e.c". Can you
please rebase patch on top of latest next-net?
Thanks,
ferruh
next prev parent reply other threads:[~2017-04-12 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 1:55 [dpdk-dev] [PATCH v7 0/3] " Qi Zhang
2017-04-04 1:55 ` [dpdk-dev] [PATCH v7 1/3] net/i40e: enable per dev PTYPE mapping table Qi Zhang
2017-04-04 1:55 ` [dpdk-dev] [PATCH v7 2/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-04-04 1:55 ` [dpdk-dev] [PATCH v7 3/3] app/testpmd: add CL for ptype mapping configure Qi Zhang
2017-04-04 9:30 ` [dpdk-dev] [PATCH v7 0/3] net/i40e: configurable PTYPE mapping Ferruh Yigit
2017-04-04 20:22 ` Thomas Monjalon
2017-04-05 5:45 ` Jianbo Liu
2017-04-05 6:01 ` Zhang, Qi Z
2017-04-07 3:25 ` [dpdk-dev] [PATCH v8 " Qi Zhang
2017-04-07 3:25 ` [dpdk-dev] [PATCH v8 1/3] net/i40e: enable per dev PTYPE mapping table Qi Zhang
2017-04-07 2:36 ` Zhang, Qi Z
2017-04-12 2:13 ` Zhang, Qi Z
2017-04-07 3:25 ` [dpdk-dev] [PATCH v8 2/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-04-12 8:36 ` Ferruh Yigit [this message]
2017-04-07 3:25 ` [dpdk-dev] [PATCH v8 3/3] app/testpmd: add CL for ptype mapping configure Qi Zhang
2017-04-12 13:55 ` [dpdk-dev] [PATCH v9 0/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-04-12 13:55 ` [dpdk-dev] [PATCH v9 1/3] net/i40e: enable per dev PTYPE mapping table Qi Zhang
2017-04-12 13:55 ` [dpdk-dev] [PATCH v9 2/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-04-12 13:55 ` [dpdk-dev] [PATCH v9 3/3] app/testpmd: add CL for ptype mapping configure Qi Zhang
2017-04-13 9:50 ` [dpdk-dev] [PATCH v9 0/3] net/i40e: configurable PTYPE mapping Chao Zhu
2017-04-13 10:46 ` Ferruh Yigit
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=dc289d69-f612-ede5-434f-e8fc816ad080@intel.com \
--to=ferruh.yigit@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jianbo.liu@linaro.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.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 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).