From: Pavel Emelyanov <xemul@virtuozzo.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 0/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request
Date: Mon, 23 Jan 2017 15:36:34 +0300 [thread overview]
Message-ID: <5885F8D2.2010305@virtuozzo.com> (raw)
In-Reply-To: <1484814154-1557-1-git-send-email-rppt@linux.vnet.ibm.com>
On 01/19/2017 11:22 AM, Mike Rapoport wrote:
> Hi,
>
> These patches add notification of madvise(MADV_REMOVE) event to
> non-cooperative userfaultfd monitor.
>
> The first pacth renames EVENT_MADVDONTNEED to EVENT_REMOVE along with
> relevant functions and structures. Using _REMOVE instead of _MADVDONTNEED
> describes the event semantics more clearly and I hope it's not too late for
> such change in the ABI.
>
> The patches are against current -mm tree.
>
> Mike Rapoport (3):
> userfaultfd: non-cooperative: rename *EVENT_MADVDONTNEED to *EVENT_REMOVE
> userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request
> userfaultfd: non-cooperative: selftest: enable REMOVE event test for shmem
Acked-by: Pavel Emelyanov <xemul@virtuozzo.com>
--
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>
prev parent reply other threads:[~2017-01-23 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 8:22 Mike Rapoport
2017-01-19 8:22 ` [PATCH 1/3] userfaultfd: non-cooperative: rename *EVENT_MADVDONTNEED to *EVENT_REMOVE Mike Rapoport
2017-01-19 8:43 ` Hillf Danton
2017-01-19 8:22 ` [PATCH 2/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request Mike Rapoport
2017-01-19 8:58 ` Hillf Danton
2017-01-19 8:22 ` [PATCH 3/3] userfaultfd: non-cooperative: selftest: enable REMOVE event test for shmem Mike Rapoport
2017-01-19 18:15 ` [PATCH 0/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request Andrea Arcangeli
2017-01-23 12:36 ` Pavel Emelyanov [this message]
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=5885F8D2.2010305@virtuozzo.com \
--to=xemul@virtuozzo.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dgilbert@redhat.com \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rppt@linux.vnet.ibm.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