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

"Dmitry V. Levin" <[email protected]> Tue, 27 Feb 2018 05:18:18 +0300

Newsgroups	gmane.linux.kernel,gmane.linux.kernel.mm,gmane.linux.file-systems,gmane.linux.kernel.api,gmane.comp.gdb.devel
Message-ID	<[email protected]>

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 <[email protected]> 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 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

signature.asc (application/pgp-signature, 801 B)