From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <h.lance.richardson@gmail.com>
Cc: dpdk-dev <dev@dpdk.org>,
Lance Richardson <lance.richardson@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] net/bnxt: fix outer checksum status
Date: Sat, 2 Jan 2021 19:42:35 -0800 [thread overview]
Message-ID: <CACZ4nhsidKRGXx0rX380cPOSZ3uKG4YYBvZp=bbryUWQvMo4wg@mail.gmail.com> (raw)
In-Reply-To: <20201218202837.2074736-1-lance604@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
On Fri, Dec 18, 2020 at 12:28 PM Lance Richardson <
h.lance.richardson@gmail.com> wrote:
> From: Lance Richardson <lance.richardson@broadcom.com>
>
> Receive checksum offload status flags in the mbuf
> ol_flags field should include inner/outer status
> only when outer checksum offload is enabled, which
> currently isn't the case for the bnxt PMD. Fix by
> using a hw-to-ol_flags mapping table that is constructed
> based on configured offloads.
>
> Lance Richardson (2):
> net/bnxt: make offload flags mapping per-ring
> net/bnxt: fix ol_flags checksum status
>
Patches applied to dpdk-next-net-brcm.
>
> drivers/net/bnxt/bnxt_rxr.c | 113 +++++++++++++++++---------
> drivers/net/bnxt/bnxt_rxr.h | 12 +--
> drivers/net/bnxt/bnxt_rxtx_vec_neon.c | 16 ++--
> drivers/net/bnxt/bnxt_rxtx_vec_sse.c | 16 ++--
> 4 files changed, 104 insertions(+), 53 deletions(-)
>
> --
> 2.25.1
>
>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
prev parent reply other threads:[~2021-01-03 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 20:28 Lance Richardson
2020-12-18 20:28 ` [dpdk-dev] [PATCH 1/2] net/bnxt: make offload flags mapping per-ring Lance Richardson
2020-12-18 20:28 ` [dpdk-dev] [PATCH 2/2] net/bnxt: fix ol_flags checksum status Lance Richardson
2021-01-03 3:42 ` Ajit Khaparde [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='CACZ4nhsidKRGXx0rX380cPOSZ3uKG4YYBvZp=bbryUWQvMo4wg@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=h.lance.richardson@gmail.com \
--cc=lance.richardson@broadcom.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).