[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 8 Aug 2012 15:26:46 +0300
From: Claudiu Manoil <claudiu.manoil@...escale.com>
To: <netdev@...r.kernel.org>
CC: "David S. Miller" <davem@...emloft.net>,
Paul Gortmaker <paul.gortmaker@...driver.com>
Subject: [RFC net-next 0/4] gianfar: Use separate NAPI for Tx confirmation processing
Hi all,
This set of patches basically splits the existing napi poll routine into
two separate napi functions, one for Rx processing (triggered by frame
receive interrupts only) and one for the Tx confirmation path processing
(triggerred by Tx confirmation interrupts only). The polling algorithm
behind remains much the same.
Important throughput improvements have been noted on low power boards with
this set of changes.
For instance, for the following netperf test:
netperf -l 20 -cC -H 192.168.10.1 -t TCP_STREAM -- -m 1500
yields a throughput gain from oscilating ~500-~700 Mbps to steady ~940 Mbps,
(if the Rx/Tx paths are processed on different cores), w/ no increase in CPU%,
on a p1020rdb - 2 core machine featuring etsec2.0 (Multi-Queue Multi-Group
driver mode).
Also, this change, which should ballance Rx and Tx processing, proves to
be effective against Rx busy interrupt occurrences.
Thanks for your review.
Claudiu
Claudiu Manoil (4):
gianfar: Remove redundant programming of [rt]xic registers
gianfar: Clear ievent from interrupt handler for [RT]x int
gianfar: Separate out the Rx and Tx coalescing functions
gianfar: Use separate NAPIs for Tx and Rx processing
drivers/net/ethernet/freescale/gianfar.c | 220 +++++++++++++++++++++--------
drivers/net/ethernet/freescale/gianfar.h | 16 ++-
2 files changed, 171 insertions(+), 65 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
Powered by blists - more mailing lists