Re: [OMPI devel] [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

> On Feb 28, 2018, at 2:12 AM, Pavel Emelyanov wrote: > > On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: >> On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: >>> On 02/21/2018 03:44 AM, Andrew Morton wrote: On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport

Re: [OMPI devel] [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

> On Feb 28, 2018, at 2:12 AM, Pavel Emelyanov wrote: > > On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: >> On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: >>> On 02/21/2018 03:44 AM, Andrew Morton wrote: On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport wrote:

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Wed, Feb 28, 2018 at 10:12:55AM +0300, Pavel Emelyanov wrote: > On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: > > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: > >> On 02/21/2018 03:44 AM, Andrew Morton wrote: > >>> On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > >>>

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Wed, Feb 28, 2018 at 10:12:55AM +0300, Pavel Emelyanov wrote: > On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: > > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: > >> On 02/21/2018 03:44 AM, Andrew Morton wrote: > >>> On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > >>>

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: >> On 02/21/2018 03:44 AM, Andrew Morton wrote: >>> On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport >>> wrote: >>> This patches introduces new

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: >> On 02/21/2018 03:44 AM, Andrew Morton wrote: >>> On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport >>> wrote: >>> This patches introduces new process_vmsplice system call that

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Tue, Feb 27, 2018 at 05:18:18AM +0300, Dmitry V. Levin wrote: > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: > > On 02/21/2018 03:44 AM, Andrew Morton wrote: > > > On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > > > wrote: > > > > > >> This

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Tue, Feb 27, 2018 at 05:18:18AM +0300, Dmitry V. Levin wrote: > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: > > On 02/21/2018 03:44 AM, Andrew Morton wrote: > > > On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > > > wrote: > > > > > >> This patches introduces new

Re: [OMPI devel] [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Mon, Feb 26, 2018 at 09:38:19AM -0700, Nathan Hjelm wrote: > All MPI implementations have support for using CMA to transfer data > between local processes. The performance is fairly good (not as good as > XPMEM) but the interface limits what we can do with to remote process > memory (no

Re: [OMPI devel] [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Mon, Feb 26, 2018 at 09:38:19AM -0700, Nathan Hjelm wrote: > All MPI implementations have support for using CMA to transfer data > between local processes. The performance is fairly good (not as good as > XPMEM) but the interface limits what we can do with to remote process > memory (no

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: > On 02/21/2018 03:44 AM, Andrew Morton wrote: > > On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > > wrote: > > > >> This patches introduces new process_vmsplice system call that combines > >>

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: > On 02/21/2018 03:44 AM, Andrew Morton wrote: > > On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > > wrote: > > > >> This patches introduces new process_vmsplice system call that combines > >> functionality of process_vm_read

Re: [OMPI devel] [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

All MPI implementations have support for using CMA to transfer data between local processes. The performance is fairly good (not as good as XPMEM) but the interface limits what we can do with to remote process memory (no atomics). I have not heard about this new proposal. What is the benefit of

Re: [OMPI devel] [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

All MPI implementations have support for using CMA to transfer data between local processes. The performance is fairly good (not as good as XPMEM) but the interface limits what we can do with to remote process memory (no atomics). I have not heard about this new proposal. What is the benefit of

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On 02/21/2018 03:44 AM, Andrew Morton wrote: > On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > wrote: > >> This patches introduces new process_vmsplice system call that combines >> functionality of process_vm_read and vmsplice. > > All seems fairly strightforward.

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On 02/21/2018 03:44 AM, Andrew Morton wrote: > On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport > wrote: > >> This patches introduces new process_vmsplice system call that combines >> functionality of process_vm_read and vmsplice. > > All seems fairly strightforward. The big question is: do

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport wrote: > This patches introduces new process_vmsplice system call that combines > functionality of process_vm_read and vmsplice. All seems fairly strightforward. The big question is: do we know that people will actually

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport wrote: > This patches introduces new process_vmsplice system call that combines > functionality of process_vm_read and vmsplice. All seems fairly strightforward. The big question is: do we know that people will actually use this, and get

[PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

Hi, This patches introduces new process_vmsplice system call that combines functionality of process_vm_read and vmsplice. It allows to map the memory of another process into a pipe, similarly to what vmsplice does for its own address space. The patch 2/4 ("vm: add a syscall to map a process

[PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

Hi, This patches introduces new process_vmsplice system call that combines functionality of process_vm_read and vmsplice. It allows to map the memory of another process into a pipe, similarly to what vmsplice does for its own address space. The patch 2/4 ("vm: add a syscall to map a process