Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	       Alexander Viro <viro@zeniv.linux.org.uk>
Cc: 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 <arnd@arndb.de>,
	       Pavel Emelyanov <xemul@virtuozzo.com>,
	       Michael Kerrisk <mtk.manpages@gmail.com>,
	       Thomas Gleixner <tglx@linutronix.de>,
	       Josh Triplett <josh@joshtriplett.org>,
	Jann Horn <jannh@google.com>,
	       Greg KH <gregkh@linuxfoundation.org>,
	Andrei Vagin <avagin@openvz.org>,
	       Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe
Date: Tue, 09 Jan 2018 06:31:00 -0000	[thread overview]
Message-ID: <1515479453-14672-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)

Hi,

This patches introduces new process_vmsplice system call that combines
functionality of process_vm_read and vmsplice.

It allows to map the memory of another process into a pipe, similarly to
what vmsplice does for its own address space.

The patch 2/4 ("vm: add a syscall to map a process memory into a pipe")
actually adds the new system call and provides its elaborate description.

The patchset is against -mm tree.

v5: update changelog with more elaborate usecase description
v4: skip test when process_vmsplice syscall is not available
v3: minor refactoring to reduce code duplication
v2: move this syscall under CONFIG_CROSS_MEMORY_ATTACH
    give correct flags to get_user_pages_remote()


Andrei Vagin (3):
  vm: add a syscall to map a process memory into a pipe
  x86: wire up the process_vmsplice syscall
  test: add a test for the process_vmsplice syscall

Mike Rapoport (1):
  fs/splice: introduce pages_to_pipe helper

 arch/x86/entry/syscalls/syscall_32.tbl             |   1 +
 arch/x86/entry/syscalls/syscall_64.tbl             |   2 +
 fs/splice.c                                        | 262 +++++++++++++++++++--
 include/linux/compat.h                             |   3 +
 include/linux/syscalls.h                           |   4 +
 include/uapi/asm-generic/unistd.h                  |   5 +-
 kernel/sys_ni.c                                    |   2 +
 tools/testing/selftests/process_vmsplice/Makefile  |   5 +
 .../process_vmsplice/process_vmsplice_test.c       | 196 +++++++++++++++
 9 files changed, 458 insertions(+), 22 deletions(-)
 create mode 100644 tools/testing/selftests/process_vmsplice/Makefile
 create mode 100644 tools/testing/selftests/process_vmsplice/process_vmsplice_test.c

-- 
2.7.4


             reply	other threads:[~2018-01-09  6:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  6:31 Mike Rapoport [this message]
2018-01-09  6:31 ` [PATCH v5 3/4] x86: wire up the process_vmsplice syscall Mike Rapoport
2018-01-09  6:31 ` [PATCH v5 2/4] vm: add a syscall to map a process memory into a pipe Mike Rapoport
2018-01-09  6:31 ` [PATCH v5 1/4] fs/splice: introduce pages_to_pipe helper Mike Rapoport
2018-01-09  6:31 ` [PATCH v5 4/4] test: add a test for the process_vmsplice syscall Mike Rapoport
2018-02-21  0:44 ` [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe Andrew Morton
2018-02-26  9:03   ` Pavel Emelyanov
2018-02-26 16:38     ` [OMPI devel] " Nathan Hjelm
2018-02-27  7:10       ` Mike Rapoport
     [not found]     ` <20180227021818.GA31386@altlinux.org>
2018-02-28  7:13       ` Pavel Emelyanov
2018-02-28 23:12         ` [OMPI devel] " Atchley, Scott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1515479453-14672-1-git-send-email-rppt@linux.vnet.ibm.com \
    --to=rppt@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=avagin@openvz.org \
    --cc=criu@openvz.org \
    --cc=devel@lists.open-mpi.org \
    --cc=gdb@sourceware.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mtk.manpages@gmail.com \
    --cc=rr-dev@mozilla.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xemul@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox