From: Hugh Dickins <hughd@google.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH]mmap: avoid unnecessary anon_vma lock
Date: Sun, 17 Apr 2011 20:05:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.00.1104172003330.22756@sister.anvils> (raw)
In-Reply-To: <1301277532.3981.25.camel@sli10-conroe>
On Mon, 28 Mar 2011, Shaohua Li wrote:
> If we only change vma->vm_end, we can avoid taking anon_vma lock even 'insert'
> isn't NULL, which is the case of split_vma.
> From my understanding, we need the lock before because rmap must get the
> 'insert' VMA when we adjust old VMA's vm_end (the 'insert' VMA is linked to
> anon_vma list in __insert_vm_struct before).
> But now this isn't true any more. The 'insert' VMA is already linked to
> anon_vma list in __split_vma(with anon_vma_clone()) instead of
> __insert_vm_struct. There is no race rmap can't get required VMAs.
> So the anon_vma lock is unnecessary, and this can reduce one locking in brk
> case and improve scalability.
>
> Signed-off-by: Shaohua Li<shaohua.li@intel.com>
I was sceptical at first, but yes, you're right: thanks.
Acked-by: Hugh Dickins <hughd@google.com>
>
> ---
> mm/mmap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux/mm/mmap.c
> ===================================================================
> --- linux.orig/mm/mmap.c 2011-03-24 09:08:27.000000000 +0800
> +++ linux/mm/mmap.c 2011-03-24 09:14:03.000000000 +0800
> @@ -605,7 +605,7 @@ again: remove_next = 1 + (end > next->
> * lock may be shared between many sibling processes. Skipping
> * the lock for brk adjustments makes a difference sometimes.
> */
> - if (vma->anon_vma && (insert || importer || start != vma->vm_start)) {
> + if (vma->anon_vma && (importer || start != vma->vm_start)) {
> anon_vma = vma->anon_vma;
> anon_vma_lock(anon_vma);
> }
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-04-18 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 1:58 Shaohua Li
2011-03-28 16:57 ` Andi Kleen
2011-03-29 22:35 ` Andrew Morton
2011-03-30 3:25 ` Andi Kleen
2011-04-18 3:05 ` Hugh Dickins [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=alpine.LSU.2.00.1104172003330.22756@sister.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.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