From: Jerin Jacob <jerinjacobk@gmail.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: Rasesh Mody <rmody@marvell.com>, dpdk-dev <dev@dpdk.org>,
Jerin Jacob <jerinj@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/3] net/qede/base: fix for FW bug
Date: Wed, 30 Oct 2019 16:55:44 +0530 [thread overview]
Message-ID: <CALBAE1Po+1kCBQ62jaqPcEDJNejwb9ZDeZTjiO-YH5iR5NjOjg@mail.gmail.com> (raw)
In-Reply-To: <1eea6d89-0921-9fae-7a7f-28bb95b9cab1@redhat.com>
On Mon, Oct 21, 2019 at 4:29 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
> On 20/10/2019 06:20, Rasesh Mody wrote:
> > In our testing we have identified a critical FW bug. Performance
> > is degraded significantly for certain packet sizes with 8.40.25.0 FW.
> >
> > This patch updates the FW to version 8.40.33.0. The updated FW has a
> > fix to performance issue.
> >
> > The patch also adds initialization for FW overlay RAM as part of
> > hardware initialization which is required by the new FW.
> >
> > Fixes: 066f0d380a2f ("net/qede/base: update FW to 8.40.25.0")
> >
>
> Hi Rasesh, it should be:
>
> Fixes: 21c959e2cb10 ("net/qede/base: update FW to 8.40.25.0")
# Updated the Fixes git id
# Added cc: stable@dpdk.org
# Changed the subject to "net/qede/base: update FW to 8.40.33.0"
Series applied to dpdk-next-net-mrvl/master. Thanks.
> > Signed-off-by: Rasesh Mody <rmody@marvell.com>
next prev parent reply other threads:[~2019-10-30 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 5:20 Rasesh Mody
2019-10-20 5:20 ` [dpdk-dev] [PATCH 2/3] net/qede: fix to modify MTU update flow Rasesh Mody
2019-10-20 5:20 ` [dpdk-dev] [PATCH 3/3] net/qede: fix to set VLAN strip mode Rasesh Mody
2019-10-21 10:58 ` [dpdk-dev] [PATCH 1/3] net/qede/base: fix for FW bug Kevin Traynor
2019-10-30 11:25 ` Jerin Jacob [this message]
2019-10-21 18:52 Rasesh Mody
2019-10-21 20:10 ` Kevin Traynor
2019-10-22 8:45 ` Ferruh Yigit
2019-10-22 9:13 ` Kevin Traynor
2019-10-30 19:15 ` Rasesh Mody
2019-10-21 20:46 Rasesh Mody
2019-10-21 21:41 ` Kevin Traynor
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=CALBAE1Po+1kCBQ62jaqPcEDJNejwb9ZDeZTjiO-YH5iR5NjOjg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=ktraynor@redhat.com \
--cc=rmody@marvell.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).