From: Ghalem Boudour <ghalem.boudour@6wind.com>
To: Marcin Wojtas <mw@semihalf.com>,
Michal Krawczyk <mk@semihalf.com>,
Guy Tzalik <gtzalik@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Igor Chauskin <igorch@amazon.com>
Cc: dev@dpdk.org, Ghalem Boudour <ghalem.boudour@6wind.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: [dpdk-dev] [PATCH] net/ena: enable multi segment in Tx offload flags
Date: Mon, 12 Jul 2021 19:01:53 +0200 [thread overview]
Message-ID: <20210712170153.11508-1-ghalem.boudour@6wind.com> (raw)
The DPDK ENA driver does not provide multi-segment tx offload capability.
Let's add DEV_TX_OFFLOAD_MULTI_SEGS to ports offload capability by default.
This flag in not listed in doc/guides/nics/features/default.ini, so
ena.ini does not need to be updated.
Signed-off-by: Ghalem Boudour <ghalem.boudour@6wind.com>
Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
---
drivers/net/ena/ena_ethdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
index dfe68279fa7b..a8422ee425ce 100644
--- a/drivers/net/ena/ena_ethdev.c
+++ b/drivers/net/ena/ena_ethdev.c
@@ -2055,6 +2055,7 @@ static int ena_infos_get(struct rte_eth_dev *dev,
DEV_RX_OFFLOAD_TCP_CKSUM;
rx_feat |= DEV_RX_OFFLOAD_JUMBO_FRAME;
+ tx_feat |= DEV_TX_OFFLOAD_MULTI_SEGS;
/* Inform framework about available features */
dev_info->rx_offload_capa = rx_feat;
--
2.28.0
next reply other threads:[~2021-07-12 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 17:01 Ghalem Boudour [this message]
2021-07-14 10:02 ` Michał Krawczyk
2021-07-28 14:27 ` Olivier Matz
2021-07-29 6:40 ` Michał Krawczyk
2021-07-29 7:26 ` Olivier Matz
2021-07-29 7:32 ` Michał Krawczyk
2021-07-30 8:34 ` [dpdk-dev] [PATCH v2] " Olivier Matz
2021-07-30 9:37 ` Michał Krawczyk
2021-07-30 10:11 ` Thomas Monjalon
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=20210712170153.11508-1-ghalem.boudour@6wind.com \
--to=ghalem.boudour@6wind.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=olivier.matz@6wind.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).