DPDK patches and discussions
 help / color / mirror / Atom feed
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 v7 0/3] net/i40e: configurable PTYPE mapping
Date: Tue, 4 Apr 2017 10:30:56 +0100	[thread overview]
Message-ID: <7f5ba680-9b10-dde5-fef2-5b245f928c93@intel.com> (raw)
In-Reply-To: <20170404015516.7784-1-qi.z.zhang@intel.com>

On 4/4/2017 2:55 AM, 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.
> 

<...>

> 
> - 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

Series applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2017-04-04  9:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04  1:55 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 ` Ferruh Yigit [this message]
2017-04-04 20:22   ` [dpdk-dev] [PATCH v7 0/3] net/i40e: configurable PTYPE mapping 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
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=7f5ba680-9b10-dde5-fef2-5b245f928c93@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).