From: Didier Pallard <didier.pallard@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/4] fix missing Tx multi segs capabilities
Date: Wed, 19 Sep 2018 17:04:05 +0200 [thread overview]
Message-ID: <20180919150409.22880-1-didier.pallard@6wind.com> (raw)
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating
that application will never send multisegmented packets, allowing
pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability
that is advertised by pmds, some of them do not advertise it and
expect to never receive fragmented packets (octeontx, axgbe)
So an ethdev that supports multisegmented packets should properly
advertise it.
Didier Pallard (4):
net/e1000: fix missing Tx multi segs capability
net/fm10k: fix missing Tx multi segs capability
net/i40e: fix missing Tx multi segs capability
net/ixgbe: fix missing Tx multi segs capability
drivers/net/e1000/em_rxtx.c | 1 +
drivers/net/fm10k/fm10k_ethdev.c | 1 +
drivers/net/i40e/i40e_vf_representor.c | 1 +
drivers/net/ixgbe/ixgbe_vf_representor.c | 2 +-
4 files changed, 4 insertions(+), 1 deletion(-)
--
2.11.0
next reply other threads:[~2018-09-19 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 15:04 Didier Pallard [this message]
2018-09-19 15:04 ` [dpdk-dev] [PATCH 1/4] net/e1000: fix missing Tx multi segs capability Didier Pallard
2018-09-19 15:04 ` [dpdk-dev] [PATCH 2/4] net/fm10k: " Didier Pallard
2018-09-19 15:04 ` [dpdk-dev] [PATCH 3/4] net/i40e: " Didier Pallard
2018-09-19 15:04 ` [dpdk-dev] [PATCH 4/4] net/ixgbe: " Didier Pallard
2018-09-19 23:29 ` [dpdk-dev] [PATCH 0/4] fix missing Tx multi segs capabilities Ananyev, Konstantin
2018-09-21 14:20 ` Zhang, Qi Z
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=20180919150409.22880-1-didier.pallard@6wind.com \
--to=didier.pallard@6wind.com \
--cc=dev@dpdk.org \
/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).