All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@pathscale.com>
To: akpm@osdl.org
Cc: rdreier@cisco.com, ak@suse.de, linux-kernel@vger.kernel.org
Subject: [PATCH 0 of 2] Much smaller MMIO copy patches
Date: Wed, 11 Jan 2006 16:29:34 -0800	[thread overview]
Message-ID: <patchbomb.1137025774@eng-12.pathscale.com> (raw)

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

These MMIO copy patches are lean, mean, and apparently clean.

These define the generic __raw_memcpy_toio32 as a weak symbol, which
arches are free to override.  We provide a specialised implementation
for x86_64.

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

These patches should apply cleanly against current -git, and have been
tested on i386 and x86_64.  The symbol shows up in the built vmlinux,
as one might hope.

The patch series is as follows:

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

x86_64-raw_memcpy_io.patch
  Add a faster __raw_memcpy_io32 routine to x86_64.

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

             reply	other threads:[~2006-01-12  0:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  0:29 Bryan O'Sullivan [this message]
2006-01-12  0:29 ` [PATCH 1 of 2] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-12  0:29 ` [PATCH 2 of 2] __raw_memcpy_toio32 for x86_64 Bryan O'Sullivan
2006-01-12  0:56   ` Andi Kleen
2006-01-12  1:21     ` Roland Dreier
2006-01-12  1:27       ` Andi Kleen
2006-01-12  1:32         ` Roland Dreier
2006-01-12  1:40           ` Andi Kleen
2006-01-12  1:27     ` Bryan O'Sullivan
2006-01-12  1:33       ` Andi Kleen
2006-01-12  4:14         ` Bryan O'Sullivan
2006-01-12  4:19           ` Andi Kleen
2006-01-12  4:32             ` Bryan O'Sullivan
2006-01-12  4:45               ` Andi Kleen
2006-01-12  5:04                 ` Bryan O'Sullivan
2006-01-12 15:54                   ` Andi Kleen

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.1137025774@eng-12.pathscale.com \
    --to=bos@pathscale.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.