From: Olivier Matz <olivier.matz@6wind.com>
To: "Michał Krawczyk" <mk@semihalf.com>
Cc: Ghalem Boudour <ghalem.boudour@6wind.com>,
Marcin Wojtas <mw@semihalf.com>, Guy Tzalik <gtzalik@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Igor Chauskin <igorch@amazon.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ena: enable multi segment in Tx offload flags
Date: Wed, 28 Jul 2021 16:27:06 +0200 [thread overview]
Message-ID: <YQFpOqupCQb+Bwjk@platinum> (raw)
In-Reply-To: <CAJMMOfNFmyekYQAgOw-VQx+Em+dsYAcCrjF_fB7XVVWD4d901Q@mail.gmail.com>
Hi Michał,
On Wed, Jul 14, 2021 at 12:02:32PM +0200, Michał Krawczyk wrote:
> pon., 12 lip 2021 o 19:03 Ghalem Boudour <ghalem.boudour@6wind.com> napisał(a):
> >
> > 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.
> >
>
> Hi Ghalem,
>
> This patch enables announcement of the DEV_TX_OFFLOAD_MULTI_SEGS
> capability, but still the application may not request this offload.
>
> As ENA PMD currently assumes all the mbufs may have multiple segments
> (and we don't have fast-path for the other cases), I suggest
> overwriting this flag in the ena_dev_configure(), similar to what
> we're doing with the DEV_RX_OFFLOAD_RSS_HASH flag.
To give some more context, our application currently checks if the
driver supports multi-segments by checking its capabilities, and asks
for the feature if it is advertised.
When dealing with drivers that do not advertise this capability, our app
linearizes the segmented mbufs before sending them to the driver.
I think this is the proper way to use the API: if the driver supports to
handle multisegmented mbufs, it should advertise the capability.
Regards,
Olivier
> Best regards,
> Michal
>
> > 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 prev parent reply other threads:[~2021-07-28 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 17:01 Ghalem Boudour
2021-07-14 10:02 ` Michał Krawczyk
2021-07-28 14:27 ` Olivier Matz [this message]
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=YQFpOqupCQb+Bwjk@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=ghalem.boudour@6wind.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.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).