From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-man@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH 0/5] {ioctl_}userfaultfd.2: initial updates for 4.11
Date: Tue, 25 Apr 2017 19:29:03 +0300 [thread overview]
Message-ID: <1493137748-32452-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)
Hello Michael,
These patches are some kind of brief highlights of the changes to the
userfaultfd pages.
The changes to userfaultfd functionality are also described at update to
Documentation/vm/userfaultfd.txt [1].
In general, there were three major additions:
* hugetlbfs support
* shmem support
* non-page fault events
I think we should add some details about using userfaultfd with different
memory types, describe meaning of each feature bits and add some text about
the new events.
I haven't updated 'struct uffd_msg' yet, and I hesitate whether it's
description belongs to userfaultfd.2 or ioctl_userfaultfd.2
As for the userfaultfd.7 we've discussed earlier, I believe it would
repeat Documentation/vm/userfaultfd.txt in way, so I'm not really sure it
is required.
--
Sincerely yours,
Mike.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5a02026d390ea1bb0c16a0e214e45613a3e3d885
Mike Rapoport (5):
userfaultfd.2: describe memory types that can be used from 4.11
ioctl_userfaultfd.2: describe memory types that can be used from 4.11
ioctl_userfaultfd.2: update UFFDIO_API description
userfaultfd.2: add Linux container migration use-case to NOTES
usefaultfd.2: add brief description of "non-cooperative" mode
man2/ioctl_userfaultfd.2 | 46 ++++++++++++++++++++++++++++++++++++++--------
man2/userfaultfd.2 | 25 ++++++++++++++++++++++---
2 files changed, 60 insertions(+), 11 deletions(-)
--
1.9.1
--
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>
next reply other threads:[~2017-04-25 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:29 Mike Rapoport [this message]
2017-04-25 16:29 ` [PATCH 1/5] userfaultfd.2: describe memory types that can be used from 4.11 Mike Rapoport
2017-04-26 6:52 ` Michael Kerrisk (man-pages)
2017-04-25 16:29 ` [PATCH 2/5] ioctl_userfaultfd.2: " Mike Rapoport
2017-04-26 6:52 ` Michael Kerrisk (man-pages)
2017-04-25 16:29 ` [PATCH 3/5] ioctl_userfaultfd.2: update UFFDIO_API description Mike Rapoport
2017-04-25 16:29 ` [PATCH 4/5] userfaultfd.2: add Linux container migration use-case to NOTES Mike Rapoport
2017-04-26 7:16 ` Michael Kerrisk (man-pages)
2017-04-25 16:29 ` [PATCH 5/5] usefaultfd.2: add brief description of "non-cooperative" mode Mike Rapoport
2017-04-26 7:18 ` Michael Kerrisk (man-pages)
2017-04-26 7:23 ` [PATCH 0/5] {ioctl_}userfaultfd.2: initial updates for 4.11 Michael Kerrisk (man-pages)
2017-04-26 7:43 ` Mike Rapoport
2017-04-26 8:43 ` Michael Kerrisk (man-pages)
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=1493137748-32452-1-git-send-email-rppt@linux.vnet.ibm.com \
--to=rppt@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.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).