From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe Date: Tue, 20 Feb 2018 16:44:06 -0800 Message-ID: <20180220164406.3ec34509376f16841dc66e34@linux-foundation.org> References: <1515479453-14672-1-git-send-email-rppt@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org In-Reply-To: <1515479453-14672-1-git-send-email-rppt@linux.vnet.ibm.com> To: Mike Rapoport Cc: Alexander Viro , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, criu@openvz.org, gdb@sourceware.org, devel@lists.open-mpi.org, rr-dev@mozilla.org, Arnd Bergmann , Pavel Emelyanov , Michael Kerrisk , Thomas Gleixner , Josh Triplett , Jann Horn , Greg KH , Andrei Vagin List-Id: linux-api@vger.kernel.org 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?