DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lingyu Liu <lingyu.liu@intel.com>
To: dev@dpdk.org, qi.z.zhang@intel.com, olivier.matz@6wind.com,
	thomas@monjalon.net, david.marchand@redhat.com
Cc: Lingyu Liu <lingyu.liu@intel.com>
Subject: [dpdk-dev] [PATCH V3 0/2] mbuf:add eCPRI hardware packet type mapping
Date: Tue, 20 Apr 2021 08:38:15 +0000	[thread overview]
Message-ID: <20210420083817.10741-1-lingyu.liu@intel.com> (raw)
In-Reply-To: <20210417092531.6001-1-lingyu.liu@intel.com>

Create eCPRI hardward packet in mbuf and add mapping in iavf.

Lingyu Liu (2):
  mbuf: support eCPRI hardware packet type
  net/iavf: update PTYPE mapping for eCPRI
---
 V3 change:
 - create patch set and add the second patch

 app/test-pmd/util.c              | 25 +++++++++------
 drivers/net/iavf/iavf_rxtx.c     | 52 ++++++++++++++++++++------------
 lib/librte_mbuf/rte_mbuf_ptype.c |  2 ++
 lib/librte_mbuf/rte_mbuf_ptype.h | 22 ++++++++++++++
 4 files changed, 72 insertions(+), 29 deletions(-)

-- 
2.25.1


  parent reply	other threads:[~2021-04-20  2:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17  9:04 [dpdk-dev] [PATCH v1] mbuf: support eCPRI hardware packet type Add L2_ETHER_ECPRI and L4_UDP_TUNNEL_ECPRI in RTE_PTYPE Lingyu Liu
2021-04-17  9:25 ` [dpdk-dev] [PATCH v2] mbuf: support eCPRI hardware packet type Lingyu Liu
2021-04-19 14:24   ` Olivier Matz
2021-04-20  2:17     ` Liu, Lingyu
2021-04-20  7:51       ` Thomas Monjalon
2021-04-20 10:06         ` Andrew Rybchenko
2021-04-22 11:09         ` Liu, Lingyu
2021-04-20 13:01       ` Bing Zhao
2021-04-20  8:38   ` Lingyu Liu [this message]
2021-04-20  8:38     ` [dpdk-dev] [PATCH V3 1/2] " Lingyu Liu
2021-04-20  9:57       ` Andrew Rybchenko
2021-04-20  8:38     ` [dpdk-dev] [PATCH V3 2/2] net/iavf: update PTYPE mapping for eCPRI Lingyu Liu

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=20210420083817.10741-1-lingyu.liu@intel.com \
    --to=lingyu.liu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=qi.z.zhang@intel.com \
    --cc=thomas@monjalon.net \
    /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).