From: Luca Boccassi <bluca@debian.org>
To: Lance Richardson <lance.richardson@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 20.11] net/bnxt: fix fallback mbuf allocation logic
Date: Mon, 08 Feb 2021 16:00:29 +0000 [thread overview]
Message-ID: <edba959085ac467d29215f881d89b496c670adfb.camel@debian.org> (raw)
In-Reply-To: <20210208151451.87164-1-lance.richardson@broadcom.com>
On Mon, 2021-02-08 at 10:14 -0500, Lance Richardson wrote:
> Error verifying signature: parse error
> Fixes for fallback mbuf allocation logic.
> - Iterate over all processed descriptors (representor and
> non-representor) when checking allocation status.
> - Invoke fallback allocation logic when an allocation
> failure has occurred for any received packet, not
> just the last.
>
> Based on upstream commit c86e930165c3 ("net/bnxt: fix fallback
> mbuf allocation logic"), with changes to resolve conflicts caused
> by the absence of upstream commit c7de4195cc4c ("net/bnxt: modify
> ring index logic")
>
> Fixes: 6dc83230b43b ("net/bnxt: support port representor data path")
> Fixes: d9dd0b29ed31 ("net/bnxt: fix Rx handling and buffer allocation logic")
> Cc: stable@dpdk.org
>
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> ---
> drivers/net/bnxt/bnxt_rxr.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>
Thanks, applied.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2021-02-08 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 15:14 Lance Richardson
2021-02-08 16:00 ` Luca Boccassi [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=edba959085ac467d29215f881d89b496c670adfb.camel@debian.org \
--to=bluca@debian.org \
--cc=ajit.khaparde@broadcom.com \
--cc=lance.richardson@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=venkatkumar.duvvuru@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).