From: "H. Peter Anvin" <hpa@zytor.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch 2.6.16-rc5-mm2] i386 memcpy: optimal memcpy for IO
Date: Thu, 01 Jun 2006 22:06:39 -0700 [thread overview]
Message-ID: <447FC75F.6090905@zytor.com> (raw)
In-Reply-To: <200606012130_MC3-1-C15B-2A16@compuserve.com>
Chuck Ebbert wrote:
> From: H. Peter Anvin <hpa@zytor.com>
>
> Optimal memcpy for moves to/from IO space. Does as few moves as
> possible while keeping transfers optimally aligned.
>
> Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
>
Why wrap this in C code when it's just assembly anyway? It just makes
it look ugly...
-hpa
next prev parent reply other threads:[~2006-06-02 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 1:28 [patch 2.6.16-rc5-mm2] i386 memcpy: optimal memcpy for IO Chuck Ebbert
2006-06-02 5:06 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-02 5:57 Chuck Ebbert
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=447FC75F.6090905@zytor.com \
--to=hpa@zytor.com \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.