From: "Hillf Danton" <hillf.zj@alibaba-inc.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>,
'Mike Kravetz' <mike.kravetz@oracle.com>,
'Pavel Emelyanov' <xemul@virtuozzo.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3] userfaultfd: non-cooperative: rename *EVENT_MADVDONTNEED to *EVENT_REMOVE
Date: Thu, 19 Jan 2017 16:43:55 +0800 [thread overview]
Message-ID: <03ad01d27230$2b57d9a0$82078ce0$@alibaba-inc.com> (raw)
In-Reply-To: <1484814154-1557-2-git-send-email-rppt@linux.vnet.ibm.com>
On Thursday, January 19, 2017 4:23 PM Mike Rapoport wrote:
>
> The UFFD_EVENT_MADVDONTNEED purpose is to notify uffd monitor about removal
> of certain range from address space tracked by userfaultfd.
> Hence, UFFD_EVENT_REMOVE seems to better reflect the operation semantics.
> Respectively, 'madv_dn' field of uffd_msg is renamed to 'remove' and the
> madvise_userfault_dontneed callback is renamed to userfaultfd_remove.
>
Looks that "no function change" is missing.
> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
> ---
Acked-by: Hillf Danton <hillf.zj@alibaba-inc.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>
next prev parent reply other threads:[~2017-01-19 8:44 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 [this message]
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
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='03ad01d27230$2b57d9a0$82078ce0$@alibaba-inc.com' \
--to=hillf.zj@alibaba-inc.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dgilbert@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox