From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 19.11 0/3] net/bnxt: backports for 19.11
Date: Tue, 17 Aug 2021 11:43:59 +0200 [thread overview]
Message-ID: <CAATJJ0KoZe9cLjMc3WWDQfLAxhEA3ShPZBO-V_2Doboq5MwBcQ@mail.gmail.com> (raw)
In-Reply-To: <20210816203702.7235-1-lance.richardson@broadcom.com>
On Mon, Aug 16, 2021 at 10:37 PM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Backported patches requiring manual conflict resolution
> for the bnxt PMD.
Thank you, applied all three to the 19.11 WIP stable branch.
> Lance Richardson (3):
> net/bnxt: fix Rx burst size constraint
> net/bnxt: fix ring and context memory allocation
> net/bnxt: fix missing barriers in completion handling
>
> drivers/net/bnxt/bnxt_cpr.h | 40 ++++++++++++++++++++++------
> drivers/net/bnxt/bnxt_ethdev.c | 18 ++++++-------
> drivers/net/bnxt/bnxt_irq.c | 6 ++---
> drivers/net/bnxt/bnxt_ring.c | 30 ++++++++++-----------
> drivers/net/bnxt/bnxt_ring.h | 2 +-
> drivers/net/bnxt/bnxt_rxq.c | 4 +--
> drivers/net/bnxt/bnxt_rxr.c | 9 ++++---
> drivers/net/bnxt/bnxt_rxtx_vec_sse.c | 40 +++++++++++++++++++++-------
> drivers/net/bnxt/bnxt_txq.c | 4 +--
> drivers/net/bnxt/bnxt_txr.c | 2 +-
> drivers/net/bnxt/bnxt_vnic.c | 3 ++-
> 11 files changed, 102 insertions(+), 56 deletions(-)
>
> --
> 2.25.1
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2021-08-17 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 20:36 Lance Richardson
2021-08-16 20:37 ` [dpdk-stable] [PATCH 19.11 1/3] net/bnxt: fix Rx burst size constraint Lance Richardson
2021-08-16 20:37 ` [dpdk-stable] [PATCH 19.11 2/3] net/bnxt: fix ring and context memory allocation Lance Richardson
2021-08-16 20:37 ` [dpdk-stable] [PATCH 19.11 3/3] net/bnxt: fix missing barriers in completion handling Lance Richardson
2021-08-17 9:43 ` Christian Ehrhardt [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=CAATJJ0KoZe9cLjMc3WWDQfLAxhEA3ShPZBO-V_2Doboq5MwBcQ@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=lance.richardson@broadcom.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).