[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3122ec5a-7f73-f6b4-33ea-8c10ef32e5b0@virtuozzo.com>
Date: Mon, 26 Feb 2018 12:02:25 +0300
From: Pavel Emelyanov <xemul@...tuozzo.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org, criu@...nvz.org, gdb@...rceware.org,
devel@...ts.open-mpi.org, rr-dev@...illa.org,
Arnd Bergmann <arnd@...db.de>,
Michael Kerrisk <mtk.manpages@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Triplett <josh@...htriplett.org>,
Jann Horn <jannh@...gle.com>,
Greg KH <gregkh@...uxfoundation.org>,
Andrei Vagin <avagin@...nvz.org>
Subject: 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 <rppt@...ux.vnet.ibm.com> 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
Powered by blists - more mailing lists