public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@pathscale.com>
To: akpm@osdl.org, ak@suse.de
Cc: linux-kernel@vger.kernel.org, hch@infradead.org, rdreier@cisco.com
Subject: [PATCH 0 of 2] MMIO copy patches, the next generation
Date: Thu, 12 Jan 2006 09:05:30 -0800	[thread overview]
Message-ID: <patchbomb.1137085530@eng-12.pathscale.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

After another round of review, here is a revised set of MMIO copy patches.

These have switched the name of the copy routine to __iowrite32_copy,
to match the naming convention in include/asm-generic/iomap.h, and at
Andi's request.  The name is double-underscored to make it clear that
the routine does not guarantee the order of writes or perform a memory
barrier; the kernel doc also explicitly states this.

These define the generic __iowrite32_copy as a weak symbol, which
arches are free to override.  We provide a specialised implementation
for x86_64.  In a change from prior versions of these patches, the x86_64
version no longer makes any assumptions about the bus breaking up 64-bit
transactions, and uses 32-bit copies directly.

We also introduce include/linux/io.h, which is tiny now, but a candidate
for later cleanups of all the per-arch asm-*/{io,iomap}.h files.

These patches should apply cleanly against current -git, and have been
tested on i386 and x86_64.

The patch series is as follows:

iomap_copy.patch
  Introduce the generic MMIO 32-bit copy routine.

x86_64-iomap_copy.patch
  Add a faster __iowrite32_copy routine to x86_64.

Signed-off-by: Bryan O'Sullivan <bos@pathscale.com>

             reply	other threads:[~2006-01-12 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 17:05 Bryan O'Sullivan [this message]
2006-01-12 17:05 ` [PATCH 1 of 2] Introduce __iowrite32_copy Bryan O'Sullivan
2006-01-12 17:05 ` [PATCH 2 of 2] Add faster __iowrite32_copy routine for x86_64 Bryan O'Sullivan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=patchbomb.1137085530@eng-12.pathscale.com \
    --to=bos@pathscale.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox