netdev - [PATCH 0/9] atl1: add napi to Atheros L1 NIC

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-next>] [day] [month] [year] [list]

Date:	Fri, 13 Apr 2012 20:09:45 +0400
From:	Tony Zelenoff <antonz@...allels.com>
To:	<davem@...emloft.net>
CC:	<antonz@...allels.com>, <netdev@...r.kernel.org>,
	<jcliburn@...il.com>, <csnook@...hat.com>, <khorenko@...allels.com>
Subject: [PATCH 0/9] atl1: add napi to Atheros L1 NIC

Added NAPI interface to the driver of Atheros L1 NIC.
RX speed reported by iperf in TCP mode (with and without -N
switch) improved by ~7 Mbps. In UDP mode the speed up is
improved by ~4 Mbps.
Also hard RX/TX rings processing with memory allocation in
interrupt handlers is not very good idea. So, fixed this.

Note: thouse patches must be applied after patch, that fix
kernel panic in this driver.
Its subject is: "atl1: fix kernel panic in case of DMA errors"

Tony Zelenoff (9):
  atl1: handle rx in separate condition
  atl1: make driver napi compatible
  atl1: add napi process of tx interrupts
  atl1: use defined functions to disable irq
  atl1: make function to set imr of card
  atl1: add value to check ability of reenabling IRQs
  atl1: enable errors and link ints when rx/tx scheduled
  atl1: do not process interrupts in cycle in handler
  atl1: do not drop rx/tx interrupts before they are scheduled

 drivers/net/ethernet/atheros/atlx/atl1.c |  171 +++++++++++++++++++-----------
 drivers/net/ethernet/atheros/atlx/atl1.h |   17 +++-
 drivers/net/ethernet/atheros/atlx/atlx.c |   15 ++-
 3 files changed, 135 insertions(+), 68 deletions(-)

--
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