linux-kernel - Re: Cross Memory Attach v3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110721145433.a77818b2.akpm@linux-foundation.org>
Date:	Thu, 21 Jul 2011 14:54:33 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Christopher Yeoh <cyeoh@....ibm.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	linux-man@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: Cross Memory Attach v3

On Tue, 19 Jul 2011 00:35:37 +0930
Christopher Yeoh <cyeoh@....ibm.com> wrote:

> Hi Andrew,
> 
> Resending with CC's as you requested. Have added information about a man
> page and what is required for arches other than x86 and powerpc which
> have already been done.
> 
> Just as a reminder of what has happened so far, repeating some content
> from previous emails about it:
> 
> The basic idea behind cross memory attach is to allow MPI programs doing
> intra-node communication to do a single copy of the message rather than
> a double copy of the message via shared memory.
> 
> The following patch attempts to achieve this by allowing a
> destination process, given an address and size from a source process, to
> copy memory directly from the source process into its own address space
> via a system call. There is also a symmetrical ability to copy from 
> the current process's address space into a destination process's
> address space.
>
> ...
>
>  arch/powerpc/include/asm/systbl.h  |    2 
>  arch/powerpc/include/asm/unistd.h  |    4 
>  arch/x86/include/asm/unistd_32.h   |    4 
>  arch/x86/kernel/syscall_table_32.S |    2 
>  fs/aio.c                           |    4 
>  fs/compat.c                        |    7 
>  fs/read_write.c                    |    8 
>  include/linux/compat.h             |    3 
>  include/linux/fs.h                 |    7 
>  include/linux/syscalls.h           |   13 +
>  mm/Makefile                        |    3 
>  mm/process_vm_access.c             |  446 +++++++++++++++++++++++++++++++++++++
>  security/keys/compat.c             |    2 
>  security/keys/keyctl.c             |    2 
>  14 files changed, 490 insertions(+), 17 deletions(-)

Confused.  Why no arch/x86/include/asm/unistd_64.h wire-up?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/