netdev - Re: [PATCH net-next v2 0/2] gianfar: Tx timeout issue

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20140310.131827.672807362272151307.davem@davemloft.net>
Date:	Mon, 10 Mar 2014 13:18:27 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	claudiu.manoil@...escale.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/2] gianfar: Tx timeout issue

From: Claudiu Manoil <claudiu.manoil@...escale.com>
Date: Fri, 7 Mar 2014 14:42:44 +0200

> There's an older Tx timeout issue showing up on etsec2 devices
> with 2 CPUs.  I pinned this issue down to processing overhead
> incurred by supporting multiple Tx/Rx rings, as explained in
> the 2nd patch below.  But before this, there's also a concurency
> issue leading to Rx/Tx spurrious interrupts, addressed by the
> 'Tx NAPI' patch below.
> The Tx timeout can be triggered with multiple Tx flows,
> 'iperf -c -N 8' commands, on a 2 CPUs etsec2 based (P1020) board.

Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html