netdev - Re: [PATCH net-next] bnx2x: don't wait for Tx completion on recovery

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20160316.192349.2127685766060437016.davem@davemloft.net>
Date:	Wed, 16 Mar 2016 19:23:49 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	Yuval.Mintz@...gic.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] bnx2x: don't wait for Tx completion on
 recovery

From: Yuval Mintz <Yuval.Mintz@...gic.com>
Date: Sun, 13 Mar 2016 21:21:48 +0200

> When driver has hit a parity event, HW can no longer write to host memory.
> As a result, Tx completions cannot be written to the host SB memory, and
> waiting for Tx completions eventually timeout.
> As driver is willing to delay as much as 1-2 seconds per Tx queue for its
> draining and this delay is sequential, the time to recover might greatly 
> lengthen needlessly in case the recovery is done under multi-connection
> traffic.
> 
> Signed-off-by: Yuval Mintz <Yuval.Mintz@...gic.com>

Applied.