[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1345598275.2659.71.camel@bwh-desktop.uk.solarflarecom.com>
Date: Wed, 22 Aug 2012 02:17:55 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>
CC: <netdev@...r.kernel.org>, <linux-net-drivers@...arflare.com>,
<x86@...nel.org>
Subject: [PATCH 0/3] x86_64, sfc: 128-bit memory-mapped I/O
Current Solarflare network controllers have 128-bit memory-mapped
registers which are normally accessed through a series of I/O
operations. However, it is also possible to access them with a single
MOVAPS instruction on x86_64, and this is measurably faster as it
requires only one PCIe transaction.
This series introduces reado(), writeo() and the corresponding raw
operations on x86_64. These could also be implemented on i386 with an
appropriate CPU selection, but it would require u128 etc. to be defined
as structure types.
The sfc driver can potentially take advantage of both 128-bit reads and
writes, but as a first step this changes only one particular write that
may be done on the data path.
Ben.
Ben Hutchings (3):
x86_64: Define 128-bit types for kernel code only
x86_64: Define 128-bit memory-mapped I/O operations
sfc: Use __raw_writeo() to perform TX descriptor push where possible
arch/x86/Kconfig.cpu | 4 ++
arch/x86/include/asm/io.h | 14 +++++++
arch/x86/include/asm/types.h | 8 ++++
arch/x86/lib/Makefile | 1 +
arch/x86/lib/oword_io.c | 65 +++++++++++++++++++++++++++++++++++
drivers/net/ethernet/sfc/bitfield.h | 3 ++
drivers/net/ethernet/sfc/io.h | 18 ++++++++-
include/linux/types.h | 12 ++++++
8 files changed, 123 insertions(+), 2 deletions(-)
create mode 100644 arch/x86/lib/oword_io.c
--
1.7.7.6
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
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