From: Christopher Yeoh <cyeoh@au1.ibm.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Cross Memory Attach v4
Date: Mon, 1 Aug 2011 12:37:38 +0930 [thread overview]
Message-ID: <20110801123738.6fd2205c@lilo> (raw)
In-Reply-To: <CAM9Y=f4p6Ch4u88K3eykoL_GjNiitJnD_OSOexKGBuXC58x_tQ@mail.gmail.com>
On Mon, 1 Aug 2011 10:06:31 +0800
Daniel J Blueman <daniel.blueman@gmail.com> wrote:
> On Jul 27, 11:30 am, Christopher Yeoh <cyeoh@au1.ibm.com> wrote:
> > Hi Andrew,
> >
> > Here's an updated version of the Cross Memory Attach patch. Changes
> > since the v3:
> >
> > - Adds x86_64 specific wire up
> > - Changes behaviour so process_vm_readv and process_vm_writev return
> > the number of bytes successfully read or written even if an error
> > occurs
> > - Adds more kernel doc interface comments
> > - rename of some internal functions (process_vm_rw_check_iovecs,
> > process_vm_rw) so they make more sense.
> >
> > Still need to do benchmarking to see if the optimisation for small
> > copies using a local on-stack array in process_vm_rw_core is worth
> > it.
> []
>
> A bit late to the party.
>
> get_user_pages_fast may be a nice win here, since the pages will
> almost always be present; it'll backoff to the locked get_user_pages
> path to handle the pathological case of swapped pages.
Can't use get_user_pages_fast here as in this case we want to get pages
from a different process.
Chris
--
cyeoh@au.ibm.com
prev parent reply other threads:[~2011-08-01 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 2:06 Cross Memory Attach v4 Daniel J Blueman
2011-08-01 3:07 ` Christopher Yeoh [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=20110801123738.6fd2205c@lilo \
--to=cyeoh@au1.ibm.com \
--cc=daniel.blueman@gmail.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 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.