mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: "Roland McGrath" <roland@redhat.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: Sat, 6 Dec 2008 16:30:24 +1000	[thread overview]
Message-ID: <21d7e9970812052230j705fc9bfi4a659378a43ca240@mail.gmail.com> (raw)
In-Reply-To: <20081205202746.7DB20FC379@magilla.sf.frob.com>

On Sat, Dec 6, 2008 at 6:27 AM, Roland McGrath <roland@redhat.com> wrote:
> There is never going to be something in memcpy that makes any magical
> kernel calls to find out about an address.  That's just loony, sorry.
> memcpy is inlined away by the compiler in good cases.  It's like you'd
> asked for "*ptr" to have magical constraints by the compiler generating
> code to ask the kernel if "ptr" is a special address.  Uh, really?
>

Yeah I didn't think it was a good idea, its what HPUX does, so that
implied it probably wasn't a good idea.

I was just hoping it might help people come up with a good idea.

Dave.

> If you can think of an efficient way to determine it and do what you need,
> then you could write optimized routines that do that in the vDSO perhaps.
>
>
> Thanks,
> Roland
>

      reply	other threads:[~2008-12-06  6:30 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
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 [this message]

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=21d7e9970812052230j705fc9bfi4a659378a43ca240@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    /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®