This is the mail archive of the
mailing list for the glibc project.
Re: IO space memcpy support for userspace.
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Dave Airlie" <airlied at gmail dot com>
- Cc: "linux-kernel at vger dot kernel dot org" <linux-kernel at vger dot kernel dot org>, libc-alpha at sources dot redhat dot com
- Date: Fri, 5 Dec 2008 12:32:04 -0500
- Subject: Re: IO space memcpy support for userspace.
- References: <firstname.lastname@example.org>
On Thu, Dec 4, 2008 at 10:40 PM, Dave Airlie <email@example.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