From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: copy_from_user_page/copy_to_user_page fix
Date: Wed, 9 Feb 2005 19:10:44 +0100 [thread overview]
Message-ID: <20050209181044.GA5740@linux-mips.org> (raw)
In-Reply-To: <20050209.225256.92587183.anemo@mba.ocn.ne.jp>
On Wed, Feb 09, 2005 at 10:52:56PM +0900, Atsushi Nemoto wrote:
> ralf> I'm going to apply this because it's a correct fix; the
> ralf> temporary mapping strategy as we've discussed for the dup_mmap
> ralf> problem would be preferable.
>
> Thank you. I agree that the temporary mapping will be more efficient
> though I chose a simple fix. I suppose a performance requirement for
> ptrace() would be less than the dup_mmap (fork()).
People have come up with creative abuses for ptrace which actually make
it a performance critical path. Especially UML should be mentioned in
this cathegory. And we're talkign about a few thousand cycles differences
per ptrace invocation.
Ralf
prev parent reply other threads:[~2005-02-09 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 9:49 copy_from_user_page/copy_to_user_page fix Atsushi Nemoto
2005-02-09 12:51 ` Ralf Baechle
2005-02-09 13:52 ` Atsushi Nemoto
2005-02-09 18:10 ` Ralf Baechle [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=20050209181044.GA5740@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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.