linux-kernel - [PATCH net-next v1 0/6] tg3: adaptive interrupt coalescing, non-napi mode

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]

Message-Id: <cover.1324059527.git.decot@googlers.com>
Date:	Fri, 16 Dec 2011 10:19:43 -0800
From:	David Decotigny <decot@...glers.com>
To:	Matt Carlson <mcarlson@...adcom.com>,
	Michael Chan <mchan@...adcom.com>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Cc:	Javier Martinez Canillas <martinez.javier@...il.com>,
	Robin Getz <rgetz@...ckfin.uclinux.org>,
	Matt Mackall <mpm@...enic.com>,
	David Decotigny <decot@...glers.com>
Subject: [PATCH net-next v1 0/6] tg3: adaptive interrupt coalescing, non-napi mode

This series implements adaptive interrupt coalescing for tg3 NIC,
improving performance substancially. It also implements non-NAPI mode
for specific system loads.

############################################
# Patch Set Summary:

David Decotigny (2):
  tg3: fix possible infinite loop
  tg3: move functions related to reset_task together

Maciej Żenczykowski (1):
  tg3: Remove IRQF_SAMPLE_RANDOM flag from internal tests

Tom Herbert (1):
  tg3: implementation of a non-NAPI mode

Ying Cai (2):
  tg3: Implement adaptive interrupt coalescing
  tg3: use netif_tx_start_queue instead of wake_queue when no
    reschedule needed

 drivers/net/ethernet/broadcom/Kconfig |    8 +
 drivers/net/ethernet/broadcom/tg3.c   |  379 ++++++++++++++++++++++++++++++---
 drivers/net/ethernet/broadcom/tg3.h   |   42 ++++
 3 files changed, 397 insertions(+), 32 deletions(-)

-- 
1.7.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/