From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: jingjing.wu@intel.com, helin.zhang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 1/3] net/i40e: enable per dev PTYPE mapping table
Date: Mon, 3 Apr 2017 11:11:54 +0100 [thread overview]
Message-ID: <14a3ae57-5fdf-ac4a-b94f-110f373c634b@intel.com> (raw)
In-Reply-To: <20170403105155.38239-2-qi.z.zhang@intel.com>
On 4/3/2017 11:51 AM, Qi Zhang wrote:
> The mapping from hardware defined packet type to software defined
> packet type is static for i40e device, the patch let each ethdev to
> to have their own copy of mapping table, this give the possibility
> that different ethdev can be set different PTYPE mapping rule which
> is the requirement to support following hardware's dynamic PTYPE
> feature.
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
> v5:
>
> - Rebase to dpdk-next-net
>
> drivers/net/i40e/i40e_ethdev.c | 1 +
> drivers/net/i40e/i40e_ethdev.h | 5 +++++
> drivers/net/i40e/i40e_ethdev_vf.c | 2 +-
> drivers/net/i40e/i40e_rxtx.c | 30 ++++++++++++++++++++++--------
> drivers/net/i40e/i40e_rxtx.h | 3 ++-
> drivers/net/i40e/i40e_rxtx_vec_neon.c | 8 +++++---
> drivers/net/i40e/i40e_rxtx_vec_sse.c | 14 ++++++++------
I40e PowerPC altivec vector PMD added recently, it is still only in
next-net, should this patch update that file too?
Thanks,
ferruh
next prev parent reply other threads:[~2017-04-03 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:51 [dpdk-dev] [PATCH v6 0/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-04-03 10:51 ` [dpdk-dev] [PATCH v6 1/3] net/i40e: enable per dev PTYPE mapping table Qi Zhang
2017-04-03 10:11 ` Ferruh Yigit [this message]
2017-04-04 0:40 ` Zhang, Qi Z
2017-04-03 10:51 ` [dpdk-dev] [PATCH v6 2/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-04-03 10:51 ` [dpdk-dev] [PATCH v6 3/3] app/testpmd: add CL for ptype mapping configure Qi Zhang
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=14a3ae57-5fdf-ac4a-b94f-110f373c634b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--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).