From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 0/3] net/i40e: configurable PTYPE mapping
Date: Fri, 31 Mar 2017 14:14:49 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115307C588@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <5a6dce3e-bc48-d2d7-2b38-fc956a692d62@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, March 31, 2017 9:57 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Zhang, Helin <helin.zhang@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 0/3] net/i40e: configurable PTYPE
> mapping
>
> On 3/30/2017 12:29 PM, Qi Zhang wrote:
> > The patch set create new APIs that help to change the mapping from
> > hardware defined packet type to software defined packet type for i40e
> NICs.
> > Keep these APIs private is because currently they are only meaningful
> > for devices that support dynamic PTYPE configuration, which may not be
> > a general device feature.
> >
> > v4:
> >
> > - Add comment to explain the "user defined" ptype.
> >
> > v3:
> >
> > - Fix compile error when CONFIG_RTE_LIBRTE_I40E_PMD=y in testpmd
> >
> > v2:
> >
> > - Add testpmd command line:
> > ptype mapping get <port_id> <valid_only>
> > ptype mapping replace <port_id> <target> <mask> <pkt_type>
> > ptype mapping reset <port_id>
> > ptype mapping update <port_id> <hw_ptype> <sw_ptype>
> >
> > - 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
> >
> > Qi Zhang (3):
> > net/i40e: enable per dev PTYPE mapping table
> > net/i40e: configurable PTYPE mapping
> > app/testpmd: add CL for ptype mapping configure
>
> Same for this patch, having merge conflicts, can you please rebase it on top
> of latest next-net?
OK
>
> Thanks,
> ferruh
prev parent reply other threads:[~2017-03-31 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 11:29 Qi Zhang
2017-03-30 11:29 ` [dpdk-dev] [PATCH v4 1/3] net/i40e: enable per dev PTYPE mapping table Qi Zhang
2017-03-30 11:29 ` [dpdk-dev] [PATCH v4 2/3] net/i40e: configurable PTYPE mapping Qi Zhang
2017-03-30 11:29 ` [dpdk-dev] [PATCH v4 3/3] app/testpmd: add CL for ptype mapping configure Qi Zhang
2017-03-31 0:43 ` [dpdk-dev] [PATCH v4 0/3] net/i40e: configurable PTYPE mapping Wu, Jingjing
2017-03-31 13:57 ` Ferruh Yigit
2017-03-31 14:14 ` Zhang, Qi Z [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=039ED4275CED7440929022BC67E706115307C588@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@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).