From: Andrea Arcangeli <aarcange@redhat.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Pavel Emelyanov <xemul@virtuozzo.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 0/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request
Date: Thu, 19 Jan 2017 19:15:14 +0100 [thread overview]
Message-ID: <20170119181514.GO10177@redhat.com> (raw)
In-Reply-To: <1484814154-1557-1-git-send-email-rppt@linux.vnet.ibm.com>
On Thu, Jan 19, 2017 at 10:22:31AM +0200, 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.
Reviewed-by: Andrea Arcangeli <aarcange@redhat.com>
Not sure if they should be folded inside -mm before they go upstream,
but if they're sent all along it probably doesn't make a difference,
it just adds one more handler.
In theory we could have differentiated MADV_REMOVE and MADV_DONTNEED
in two different events, but I couldn't see any downside in sharing
the same event for both and this looks more compact.
Thanks,
Andrea
--
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 prev parent reply other threads:[~2017-01-19 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 8:22 [PATCH 0/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request 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 ` Andrea Arcangeli [this message]
2017-01-23 12:36 ` [PATCH 0/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request Pavel Emelyanov
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=20170119181514.GO10177@redhat.com \
--to=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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.