From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
libc-alpha@sources.redhat.com
Subject: Re: IO space memcpy support for userspace.
Date: Fri, 5 Dec 2008 12:32:04 -0500 [thread overview]
Message-ID: <119aab440812050932h9173a4bm79273b7ea8fe9a3a@mail.gmail.com> (raw)
In-Reply-To: <21d7e9970812041940h29994c60w3e7bcf20b96efe04@mail.gmail.com>
On Thu, Dec 4, 2008 at 10:40 PM, Dave Airlie <airlied@gmail.com> wrote:
> I'm sure this has come up before and I'm sure I'll either wish I never
> posted this or someone will show me the crisp corpse of the last guy
> who suggested it.
Do you plan to prevent the compiler from issuing the same sorts of
instructions that might appear in an optimized memcpy?
Isn't it dangerous to have memory that doesn't behave like normal
memory, and yet try to treat it like normal memory?
This mismatch of abstractions is a warning that must not be ignored.
IMHO you need a thin library with a new API (adding support for HAL
would be a clever way to check for PCI devices and perhaps even
mappings).
Cheers,
Carlos.
next prev parent reply other threads:[~2008-12-05 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 3:40 Dave Airlie
2008-12-05 17:32 ` Carlos O'Donell [this message]
2008-12-05 20:22 ` David Miller
2008-12-06 6:34 ` Dave Airlie
2008-12-06 16:07 ` Carlos O'Donell
2008-12-08 5:24 ` Robert Hancock
2008-12-05 20:27 ` Roland McGrath
2008-12-06 6:30 ` Dave Airlie
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=119aab440812050932h9173a4bm79273b7ea8fe9a3a@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=airlied@gmail.com \
--cc=libc-alpha@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®