All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Andi Kleen <ak@suse.de>
Cc: "Bryan O'Sullivan" <bos@pathscale.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2 of 2] __raw_memcpy_toio32 for x86_64
Date: Wed, 11 Jan 2006 17:32:03 -0800	[thread overview]
Message-ID: <ada64oqi63w.fsf@cisco.com> (raw)
In-Reply-To: <200601120227.45209.ak@suse.de> (Andi Kleen's message of "Thu, 12 Jan 2006 02:27:44 +0100")

    Andi> Well then they can just as well use normal memcpy as long as
    Andi> they don't pass any sizes % 4 != 0. That should be ok as
    Andi> long as they add a comment there.

But then the driver will be doing memcpy() to I/O memory, which may
work by chance on x86_64 but will blow up on other archs.

 - R.

  reply	other threads:[~2006-01-12  1:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  0:29 [PATCH 0 of 2] Much smaller MMIO copy patches Bryan O'Sullivan
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 [this message]
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=ada64oqi63w.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=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.