From: Thomas Monjalon <thomas@monjalon.net>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, "Ghalem Boudour" <ghalem.boudour@6wind.com>,
"Schmeilin, Evgeny" <evgenys@amazon.com>,
"Chauskin, Igor" <igorch@amazon.com>,
"Marcin Wojtas" <mw@semihalf.com>,
stable@dpdk.org, "Michał Krawczyk" <mk@semihalf.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ena: enable multi segment in Tx offload flags
Date: Fri, 30 Jul 2021 12:11:49 +0200 [thread overview]
Message-ID: <31302762.QpVCsNjn6A@thomas> (raw)
In-Reply-To: <CAJMMOfOmkW49-awFfA+NV0LACSfH7yugYxxhbuXtUHhstMz5dw@mail.gmail.com>
30/07/2021 11:37, Michał Krawczyk:
> pt., 30 lip 2021 o 10:35 Olivier Matz <olivier.matz@6wind.com> napisał(a):
> >
> > From: Ghalem Boudour <ghalem.boudour@6wind.com>
> >
> > 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, and always set it in dev->data->dev_conf.txmode.offload.
> >
> > This flag in not listed in doc/guides/nics/features/default.ini, so
> > ena.ini does not need to be updated.
> >
> > Fixes: 1173fca25af9 ("ena: add polling-mode driver")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ghalem Boudour <ghalem.boudour@6wind.com>
> > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> Acked-by: Michal Krawczyk <mk@semihalf.com>
Applied, thanks.
prev parent reply other threads:[~2021-07-30 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 17:01 [dpdk-dev] [PATCH] " Ghalem Boudour
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 [this message]
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=31302762.QpVCsNjn6A@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=ghalem.boudour@6wind.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=olivier.matz@6wind.com \
--cc=stable@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).