Thread (15 messages) 15 messages, 8 authors, 2018-02-28

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

From: Dmitry V. Levin <hidden>
Date: 2018-02-27 02:18:18
Also in: linux-fsdevel, linux-mm, lkml

On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote:
On 02/21/2018 03:44 AM, Andrew Morton wrote:
quoted
On Tue,  9 Jan 2018 08:30:49 +0200 Mike Rapoport [off-list ref] wrote:
quoted
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 sufficient value from it to
justify its addition?
Yes, that's what bothers us a lot too :) I've tried to start with finding out if anyone 
used the sys_read/write_process_vm() calls, but failed :( Does anybody know how popular
these syscalls are?
Well, process_vm_readv itself is quite popular, it's used by debuggers nowadays,
see e.g.
$ strace -qq -esignal=none -eprocess_vm_readv strace -qq -o/dev/null cat /dev/null


-- 
ldv

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help