From: Hugh Dickins <hughd@google.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: "Kirill A. Shutemov" <kirill.shutemov@intel.linux.com>,
Michel Lespinasse <walken@google.com>,
akpm@linux-foundation.org, hughd@google.com, riel@redhat.com,
mgorman@suse.de, peterz@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, dbueso@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH 08/10] mm/mremap: share the i_mmap_rwsem
Date: Mon, 3 Nov 2014 22:04:24 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1411032148230.15596@eggly.anvils> (raw)
In-Reply-To: <1414697657-1678-9-git-send-email-dave@stgolabs.net>
I'm glad to see this series back, and nicely presented: thank you.
Not worth respinning them, but consider 1,2,3,4,5,6,7 and 9 as
Acked-by: Hugh Dickins <hughd@google.com>
On Thu, 30 Oct 2014, Davidlohr Bueso wrote:
> As per the comment in move_ptes(), we only require taking the
> anon vma and i_mmap locks to ensure that rmap will always observe
> either the old or new ptes, in the case of need_rmap_lock=true.
> No modifications to the tree itself, thus share the i_mmap_rwsem.
>
> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@intel.linux.com>
But this one is Nacked by me. I don't understand how you and Kirill
could read Michel's painstaking comment on need_rmap_locks, then go
go ahead and remove the exclusion of rmap_walk().
I agree the code here does not modify the interval tree, but the
comment explains how we're moving a pte from one place in the tree
to another, and in some cases there's a danger that the rmap walk
might miss the pte from both places (which doesn't matter much to
most of its uses, but is critical in page migration).
Or am I the one missing something?
Hugh
> ---
> mm/mremap.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/mremap.c b/mm/mremap.c
> index c929324..09bd644 100644
> --- a/mm/mremap.c
> +++ b/mm/mremap.c
> @@ -119,7 +119,7 @@ static void move_ptes(struct vm_area_struct *vma, pmd_t *old_pmd,
> if (need_rmap_locks) {
> if (vma->vm_file) {
> mapping = vma->vm_file->f_mapping;
> - i_mmap_lock_write(mapping);
> + i_mmap_lock_read(mapping);
> }
> if (vma->anon_vma) {
> anon_vma = vma->anon_vma;
> @@ -156,7 +156,7 @@ static void move_ptes(struct vm_area_struct *vma, pmd_t *old_pmd,
> if (anon_vma)
> anon_vma_unlock_read(anon_vma);
> if (mapping)
> - i_mmap_unlock_write(mapping);
> + i_mmap_unlock_read(mapping);
> }
>
> #define LATENCY_LIMIT (64 * PAGE_SIZE)
> --
> 1.8.4.5
--
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:[~2014-11-04 6:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 19:34 [PATCH v2 -next 00/10] mm: improve usage of the i_mmap lock Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 01/10] mm,fs: introduce helpers around the i_mmap_mutex Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 02/10] mm: use new helper functions " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 03/10] mm: convert i_mmap_mutex to rwsem Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 04/10] mm/rmap: share the i_mmap_rwsem Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 05/10] uprobes: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 06/10] mm/xip: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 07/10] mm/memory-failure: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 08/10] mm/mremap: " Davidlohr Bueso
2014-11-04 6:04 ` Hugh Dickins [this message]
2014-11-04 12:29 ` Kirill A. Shutemov
2014-10-30 19:34 ` [PATCH 09/10] mm/nommu: " Davidlohr Bueso
2014-10-30 19:34 ` [PATCH 10/10] mm/hugetlb: " Davidlohr Bueso
2014-11-04 6:35 ` Hugh Dickins
2014-11-05 0:59 ` Davidlohr Bueso
2014-11-05 16:04 ` Hugh Dickins
2014-11-10 16:22 ` Mel Gorman
2014-11-03 8:17 ` [PATCH v2 -next 00/10] mm: improve usage of the i_mmap lock Peter Zijlstra
2014-11-10 16:28 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2014-10-24 22:06 [PATCH " Davidlohr Bueso
2014-10-24 22:06 ` [PATCH 08/10] mm/mremap: share the i_mmap_rwsem Davidlohr Bueso
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=alpine.LSU.2.11.1411032148230.15596@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=kirill.shutemov@intel.linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=walken@google.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