From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [RFC 0/3] ethdev: add ptype as Rx offload
Date: Tue, 6 Aug 2019 13:32:01 +0530 [thread overview]
Message-ID: <20190806080206.1572-1-pbhagavatula@marvell.com> (raw)
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Add PTYPE to DEV_RX_OFFLOAD_* flags.
Currently, most of the NICs already support PTYPE parsing and update
the mbuf->packet_type through an internal lookup table, but there is
no way to disable the lookup if the application is not intrested in
ptypes returned by `rte_eth_dev_get_supported_ptypes`.
Pavan Nikhilesh (3):
ethdev: add ptype as an Rx offload
net: update Rx offload capabilities
examples: add Rx ptype offload
doc/guides/nics/features.rst | 3 +++
drivers/net/atlantic/atl_ethdev.c | 3 ++-
drivers/net/bnxt/bnxt_ethdev.c | 3 ++-
drivers/net/cxgbe/cxgbe.h | 3 ++-
drivers/net/dpaa/dpaa_ethdev.c | 3 ++-
drivers/net/dpaa2/dpaa2_ethdev.c | 3 ++-
drivers/net/e1000/em_rxtx.c | 3 ++-
drivers/net/e1000/igb_rxtx.c | 3 ++-
drivers/net/enetc/enetc_ethdev.c | 3 ++-
drivers/net/enic/enic_res.c | 3 ++-
drivers/net/failsafe/failsafe_ops.c | 6 ++++--
drivers/net/fm10k/fm10k_ethdev.c | 15 ++++++++-------
drivers/net/i40e/i40e_ethdev.c | 3 ++-
drivers/net/iavf/iavf_ethdev.c | 3 ++-
drivers/net/ice/ice_ethdev.c | 3 ++-
drivers/net/ixgbe/ixgbe_rxtx.c | 3 ++-
drivers/net/mlx4/mlx4_rxq.c | 3 ++-
drivers/net/mlx5/mlx5_rxq.c | 3 ++-
drivers/net/mvneta/mvneta_ethdev.h | 3 ++-
drivers/net/mvpp2/mrvl_ethdev.c | 3 ++-
drivers/net/netvsc/hn_rndis.c | 3 ++-
drivers/net/nfp/nfp_net.c | 3 ++-
drivers/net/octeontx/octeontx_ethdev.h | 3 ++-
drivers/net/octeontx2/otx2_ethdev.c | 5 +++++
drivers/net/octeontx2/otx2_ethdev.h | 15 ++++++++-------
drivers/net/qede/qede_ethdev.c | 3 ++-
drivers/net/tap/rte_eth_tap.c | 3 ++-
drivers/net/thunderx/nicvf_ethdev.h | 3 ++-
drivers/net/vmxnet3/vmxnet3_ethdev.c | 3 ++-
examples/ip_fragmentation/main.c | 7 +++++++
examples/l3fwd-power/main.c | 8 ++++++++
examples/l3fwd/main.c | 9 +++++++++
examples/performance-thread/l3fwd-thread/main.c | 9 +++++++++
examples/tep_termination/vxlan_setup.c | 1 +
lib/librte_ethdev/rte_ethdev.h | 1 +
35 files changed, 111 insertions(+), 40 deletions(-)
--
2.17.1
next reply other threads:[~2019-08-06 8:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:02 pbhagavatula [this message]
2019-08-06 8:02 ` [dpdk-dev] [RFC 1/3] ethdev: add ptype as an " pbhagavatula
2019-08-06 9:00 ` Andrew Rybchenko
2019-08-06 14:31 ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2019-08-06 15:45 ` Stephen Hemminger
2019-08-06 18:03 ` Andrew Rybchenko
2019-08-06 8:02 ` [dpdk-dev] [RFC 2/3] net: update Rx offload capabilities pbhagavatula
2019-08-06 8:02 ` [dpdk-dev] [RFC 3/3] examples: add Rx ptype offload pbhagavatula
2019-08-06 9:20 ` Ananyev, Konstantin
2019-08-06 13:57 ` Pavan Nikhilesh Bhagavatula
2019-08-06 8:19 ` [dpdk-dev] [RFC 0/3] ethdev: add ptype as Rx offload Hemant Agrawal
2019-08-06 8:47 ` Pavan Nikhilesh Bhagavatula
2019-08-06 9:06 ` Andrew Rybchenko
2019-08-06 23:15 ` Stephen Hemminger
2019-08-07 2:04 Jerin Jacob Kollanukkaran
2019-08-07 8:32 ` Andrew Rybchenko
2019-08-07 15:22 ` Stephen Hemminger
2019-08-07 15:44 ` Andrew Rybchenko
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=20190806080206.1572-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).