All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@pathscale.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0 of 3] 32-bit MMIO copy routine
Date: Fri,  6 Jan 2006 12:26:33 -0800	[thread overview]
Message-ID: <patchbomb.1136579193@eng-12.pathscale.com> (raw)

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

Following some discussion with Roland, and patterned after the style
anointed by Linus last week, here is a new version of the 32-bit MMIO
copy routine needed by our InfiniPath device.

The name of the routine has changed from memcpy_toio32 to
__raw_memcpy_toio32.  This reflects the basic nature of the routine;
it dodes not guarantee the order in which writes are performed, nor does
it perform a memory barrier after it is done.

The reason for this is that our chip treats the first and last writes
to some MMIO regions specially; our driver performs those directly using
writel, and uses __raw_memcpy_toio32 for the bits in between.

Regarding the specialised x86_64 implementation, Andi Kleen asked me
to perform some measurements of its performance impact.  It makes a
difference of about 5% in performance on moderately large copies over
the HyperTransport bus, compared to the generic implementation.

	<b

             reply	other threads:[~2006-01-06 20:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 20:26 Bryan O'Sullivan [this message]
2006-01-06 20:26 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-10  9:18   ` Andrew Morton
2006-01-10 14:55     ` Roland Dreier
2006-01-10 16:07       ` Bryan O'Sullivan
2006-01-10 16:56         ` [PATCH] [RFC] Generic 32-bit MMIO copy, out of line Bryan O'Sullivan
2006-01-10 17:07         ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Christoph Hellwig
2006-01-10 17:13           ` Bryan O'Sullivan
2006-01-10 17:49           ` Bryan O'Sullivan
2006-01-10 17:51             ` Christoph Hellwig
2006-01-10 17:55               ` Bryan O'Sullivan
2006-01-10 22:05                 ` Andrew Morton
2006-01-10 22:29                   ` Bryan O'Sullivan
2006-01-10 23:32                     ` Andrew Morton
2006-01-11 17:20                       ` Bryan O'Sullivan
2006-01-11 17:22                         ` Sam Ravnborg
2006-01-11 17:30                           ` Andrew Morton
2006-01-11 17:43                             ` Bryan O'Sullivan
2006-01-11 18:49                               ` Roland Dreier
2006-01-11 18:57                                 ` Bryan O'Sullivan
2006-01-11 19:01                                   ` Roland Dreier
2006-01-11 19:08                                     ` Bryan O'Sullivan
2006-01-13 15:19                       ` Adrian Bunk
2006-01-10 18:02               ` Randy.Dunlap
2006-01-10 20:04         ` Sam Ravnborg
2006-01-10 15:59     ` Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 2 of 3] memcpy32 for x86_64 Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 3 of 3] Add __raw_memcpy_toio32 to each arch 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.1136579193@eng-12.pathscale.com \
    --to=bos@pathscale.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.