[lkml]   [2018]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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 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? If its users operate on big amount of memory, they could benefit from
the proposed splice extension.

-- Pavel

 \ /
  Last update: 2018-02-26 10:03    [W:0.157 / U:0.180 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site