From: Haiyue Wang <haiyue.wang@intel.com>
To: xiaolong.ye@intel.com, dev@dpdk.org, ferruh.yigit@intel.com,
thomas@monjalon.net, olivier.matz@6wind.com
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-dev] [PATCH v10 0/2] net/ice: optimize protocol extraction by dynamic mbuf API
Date: Fri, 8 Nov 2019 23:44:33 +0800 [thread overview]
Message-ID: <20191108154435.80841-1-haiyue.wang@intel.com> (raw)
In-Reply-To: <20191105011918.53434-1-haiyue.wang@intel.com>
v10: - Rename the exported variables with 'rte_net_ice' and 'RTE_'. Update
the commit message, and separate patch for doxygen.
v9: - Rename the dynamic filed and flags variables to _offs, _mask, so it
matches the design.
v8: - Cleanup the doxgen, rename the dynamic filed and flags with ice prefix.
v7: - Change the log level from ERR to DEBUG for a successful registration,
ERR is used to develop firstly.
v6: - Don't need to register all flags when if one dev_args is set, register
it as required.
v5: - Remove the '_OL/_ol' in dynamic mbuf flag to make the variable clean.
v4: - Include the 'rte_pmd_ice.h' header in ICE source as needed, reduce
its compile scope.
v3: - Use the conventions name "rte_net_<pmd>_dynfield_<name>" since it
is defined in a in PMD.
- Add helpers API for easiy access.
v2: - disable the protocol extraction if failed to register some ol_flags
- rewrite the commit message
Haiyue Wang (2):
net/ice: optimize protocol extraction by dynamic mbuf API
doc: add the ice PMD doxygen
doc/api/doxy-api-index.md | 1 +
doc/api/doxy-api.conf.in | 1 +
doc/guides/nics/ice.rst | 14 +-
drivers/net/ice/ice_ethdev.c | 84 ++++++-
drivers/net/ice/ice_ethdev.h | 9 +
drivers/net/ice/ice_rxtx.c | 88 ++++---
drivers/net/ice/ice_rxtx.h | 1 -
drivers/net/ice/rte_pmd_ice.h | 313 +++++++++++++++---------
drivers/net/ice/rte_pmd_ice_version.map | 12 +
9 files changed, 370 insertions(+), 153 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2019-11-08 15:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 17:44 [dpdk-dev] [PATCH v1] net/ice: use dynamic mbuf API to handle protocol extraction Haiyue Wang
2019-10-29 7:34 ` [dpdk-dev] [PATCH v2] net/ice: optimize protocol extraction by dynamic mbuf API Haiyue Wang
2019-10-30 16:56 ` Olivier Matz
2019-10-31 1:16 ` Wang, Haiyue
2019-11-01 3:17 ` [dpdk-dev] [PATCH v3] " Haiyue Wang
2019-11-01 12:53 ` [dpdk-dev] [PATCH v4] " Haiyue Wang
2019-11-01 16:19 ` [dpdk-dev] [PATCH v5] " Haiyue Wang
2019-11-05 1:19 ` [dpdk-dev] [PATCH v6] " Haiyue Wang
2019-11-05 1:26 ` [dpdk-dev] [PATCH v7] " Haiyue Wang
2019-11-07 5:35 ` [dpdk-dev] [PATCH v8] " Haiyue Wang
2019-11-07 9:08 ` Ye Xiaolong
2019-11-07 10:38 ` Wang, Haiyue
2019-11-07 10:44 ` [dpdk-dev] [PATCH v9] " Haiyue Wang
2019-11-08 2:35 ` Ye Xiaolong
2019-11-08 12:34 ` Thomas Monjalon
2019-11-08 14:08 ` Wang, Haiyue
2019-11-08 14:39 ` Thomas Monjalon
2019-11-08 15:04 ` Wang, Haiyue
2019-11-08 15:03 ` Ye Xiaolong
2019-11-08 12:55 ` Thomas Monjalon
2019-11-08 14:01 ` Wang, Haiyue
2019-11-08 14:38 ` Thomas Monjalon
2019-11-08 15:44 ` Haiyue Wang [this message]
2019-11-08 15:44 ` [dpdk-dev] [PATCH v10 1/2] " Haiyue Wang
2019-11-08 15:44 ` [dpdk-dev] [PATCH v10 2/2] doc: add the ice PMD doxygen Haiyue Wang
2019-11-08 15:58 ` [dpdk-dev] [PATCH v10 0/2] net/ice: optimize protocol extraction by dynamic mbuf API Thomas Monjalon
2019-11-09 1:31 ` Ye Xiaolong
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=20191108154435.80841-1-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=thomas@monjalon.net \
--cc=xiaolong.ye@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).