linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Hugh Dickins <hughd@google.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Hillf Danton <hillf.zj@alibaba-inc.com>,
	Pavel Emelyanov <xemul@virtuozzo.com>,
	linux mm <linux-mm@kvack.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH 0/7] userfaultfd: enable zeropage support for shmem
Date: Tue, 20 Jun 2017 09:20:45 +0300	[thread overview]
Message-ID: <1497939652-16528-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)

Hi,

These patches enable support for UFFDIO_ZEROPAGE for shared memory.

The first two patches are not strictly related to userfaultfd, they are
just minor refactoring to reduce amount of code duplication.

Mike Rapoport (7):
  shmem: shmem_charge: verify max_block is not exceeded before inode update
  shmem: introduce shmem_inode_acct_block
  userfaultfd: shmem: add shmem_mfill_zeropage_pte for userfaultfd support
  userfaultfd: mcopy_atomic: introduce mfill_atomic_pte helper
  userfaultfd: shmem: wire up shmem_mfill_zeropage_pte
  userfaultfd: report UFFDIO_ZEROPAGE as available for shmem VMAs
  userfaultfd: selftest: enable testing of UFFDIO_ZEROPAGE for shmem

 fs/userfaultfd.c                         |  10 +-
 include/linux/shmem_fs.h                 |   6 ++
 mm/shmem.c                               | 167 +++++++++++++++++--------------
 mm/userfaultfd.c                         |  48 ++++++---
 tools/testing/selftests/vm/userfaultfd.c |   2 +-
 5 files changed, 136 insertions(+), 97 deletions(-)

-- 
2.7.4

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2017-06-20  6:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  6:20 Mike Rapoport [this message]
2017-06-20  6:20 ` [PATCH 1/7] shmem: shmem_charge: verify max_block is not exceeded before inode update Mike Rapoport
2017-06-20  6:20 ` [PATCH 2/7] shmem: introduce shmem_inode_acct_block Mike Rapoport
2017-06-20  6:20 ` [PATCH 3/7] userfaultfd: shmem: add shmem_mfill_zeropage_pte for userfaultfd support Mike Rapoport
2017-06-20  6:20 ` [PATCH 4/7] userfaultfd: mcopy_atomic: introduce mfill_atomic_pte helper Mike Rapoport
2017-06-20  6:20 ` [PATCH 5/7] userfaultfd: shmem: wire up shmem_mfill_zeropage_pte Mike Rapoport
2017-06-20  6:20 ` [PATCH 6/7] userfaultfd: report UFFDIO_ZEROPAGE as available for shmem VMAs Mike Rapoport
2017-06-20  6:20 ` [PATCH 7/7] userfaultfd: selftest: enable testing of UFFDIO_ZEROPAGE for shmem Mike Rapoport
2017-06-30  9:20 ` [PATCH 0/7] userfaultfd: enable zeropage support " Mike Rapoprt

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=1497939652-16528-1-git-send-email-rppt@linux.vnet.ibm.com \
    --to=rppt@linux.vnet.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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;
as well as URLs for NNTP newsgroup(s).