From: Wei Dai <wei.dai@intel.com>
To: wenzhuo.lu@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, Wei Dai <wei.dai@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] net/e1000: convert to new Rx/Tx offloads API
Date: Tue, 3 Apr 2018 10:54:54 +0800 [thread overview]
Message-ID: <20180403025456.735-1-wei.dai@intel.com> (raw)
In-Reply-To: <20180301185431.26204-1-wei.dai@intel.com>
This patch set convert net/e1000 to new Rx/Tx offloads API.
All Rx offloads are per port features.
All Tx offloads of e1000 are per queue and also per packet as they
are enabled in Tx descriptor.
In the new offload API, per queue offload only need to be set in
queue_setup(). So if the maimum number of queues is only one in
Rx or Tx path, let all offloads in the path are per queue for better
convenience.
---
v2: add offloads checking
Wei Dai (2):
net/e1000: convert to new Rx offloads API
net/e1000: convert to new Tx offloads API
drivers/net/e1000/e1000_ethdev.h | 14 ++++
drivers/net/e1000/em_ethdev.c | 58 ++++++++++----
drivers/net/e1000/em_rxtx.c | 155 +++++++++++++++++++++++++++++++++---
drivers/net/e1000/igb_ethdev.c | 60 +++++++-------
drivers/net/e1000/igb_rxtx.c | 167 +++++++++++++++++++++++++++++++++++----
5 files changed, 385 insertions(+), 69 deletions(-)
--
2.9.5
next prev parent reply other threads:[~2018-04-03 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 18:54 [dpdk-dev] [PATCH " Wei Dai
2018-03-01 18:54 ` [dpdk-dev] [PATCH 1/2] net/e1000: convert to new Rx " Wei Dai
2018-03-01 18:54 ` [dpdk-dev] [PATCH 2/2] net/e1000: convert to new Tx " Wei Dai
2018-04-03 2:54 ` Wei Dai [this message]
2018-04-03 2:54 ` [dpdk-dev] [PATCH v2 1/2] net/e1000: convert to new Rx " Wei Dai
2018-04-03 2:54 ` [dpdk-dev] [PATCH v2 2/2] net/e1000: convert to new Tx " Wei Dai
2018-04-03 13:41 ` [dpdk-dev] [PATCH v2 0/2] net/e1000: convert to new Rx/Tx " Zhang, Qi Z
2018-04-03 15:15 ` Zhang, Helin
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=20180403025456.735-1-wei.dai@intel.com \
--to=wei.dai@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@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).