From: Thomas Monjalon <thomas@monjalon.net>
To: Rasesh Mody <rasesh.mody@cavium.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, Dept-EngDPDKDev@cavium.com,
stable@dpdk.org
Subject: Re: [PATCH] net/bnx2x: fix FW cmd timeout duting device stop
Date: Thu, 02 Aug 2018 22:04:37 +0200 [thread overview]
Message-ID: <1948766.BvSm5WrXA4@xps> (raw)
In-Reply-To: <1533147560-10897-1-git-send-email-rasesh.mody@cavium.com>
01/08/2018 20:19, Rasesh Mody:
> This patch fixes firmware command timeout error seen during device stop
> while stopping queues. It patially reverts an earlier preventive change
> commit 91b7e432bcef ("net/bnx2x: disable fast path interrupts") to now
> enable fast path interrupts.
>
> The original issue of performance degradation is not observed anymore,
> with or without the fix.
>
> Fixes: 91b7e432bcef ("net/bnx2x: disable fast path interrupts")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
Applied, thanks
prev parent reply other threads:[~2018-08-02 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:19 [PATCH] net/bnx2x: fix FW cmd timeout duting device stop Rasesh Mody
2018-08-02 20:04 ` 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=1948766.BvSm5WrXA4@xps \
--to=thomas@monjalon.net \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=rasesh.mody@cavium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.