All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
	Andrea Arcangeli <aarcange@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Subject: Re: [PATCH 4/5] always lock the root (oldest) anon_vma
Date: Thu, 27 May 2010 22:55:07 +0900	[thread overview]
Message-ID: <20100527135356.GD2112@barrios-desktop> (raw)
In-Reply-To: <20100526154044.2769e707@annuminas.surriel.com>

On Wed, May 26, 2010 at 03:40:44PM -0400, Rik van Riel wrote:
> Subject: always lock the root (oldest) anon_vma
> 
> Always (and only) lock the root (oldest) anon_vma whenever we do something in an
> anon_vma.  The recently introduced anon_vma scalability is due to the rmap code
> scanning only the VMAs that need to be scanned.  Many common operations still
> took the anon_vma lock on the root anon_vma, so always taking that lock is not
> expected to introduce any scalability issues.
> 
> However, always taking the same lock does mean we only need to take one lock,
> which means rmap_walk on pages from any anon_vma in the vma is excluded from
> occurring during an munmap, expand_stack or other operation that needs to
> exclude rmap_walk and similar functions.
> 
> Also add the proper locking to vma_adjust.
> 
> Signed-off-by: Rik van Riel <riel@redhat.com>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>

Nitpick:

It would be better to modify comment about head of anon_vma in rmap.h, too.
/*  
 * NOTE: the LSB of the head.next is set by
                   ->   root->hext.next 
-- 
Kind regards,
Minchan Kim

WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan.kim@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
	Andrea Arcangeli <aarcange@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Subject: Re: [PATCH 4/5] always lock the root (oldest) anon_vma
Date: Thu, 27 May 2010 22:55:07 +0900	[thread overview]
Message-ID: <20100527135356.GD2112@barrios-desktop> (raw)
In-Reply-To: <20100526154044.2769e707@annuminas.surriel.com>

On Wed, May 26, 2010 at 03:40:44PM -0400, Rik van Riel wrote:
> Subject: always lock the root (oldest) anon_vma
> 
> Always (and only) lock the root (oldest) anon_vma whenever we do something in an
> anon_vma.  The recently introduced anon_vma scalability is due to the rmap code
> scanning only the VMAs that need to be scanned.  Many common operations still
> took the anon_vma lock on the root anon_vma, so always taking that lock is not
> expected to introduce any scalability issues.
> 
> However, always taking the same lock does mean we only need to take one lock,
> which means rmap_walk on pages from any anon_vma in the vma is excluded from
> occurring during an munmap, expand_stack or other operation that needs to
> exclude rmap_walk and similar functions.
> 
> Also add the proper locking to vma_adjust.
> 
> Signed-off-by: Rik van Riel <riel@redhat.com>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>

Nitpick:

It would be better to modify comment about head of anon_vma in rmap.h, too.
/*  
 * NOTE: the LSB of the head.next is set by
                   ->   root->hext.next 
-- 
Kind regards,
Minchan Kim

--
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>

  parent reply	other threads:[~2010-05-27 13:55 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 19:38 [PATCH -v3 0/5] always lock the root anon_vma Rik van Riel
2010-05-26 19:38 ` Rik van Riel
2010-05-26 19:38 ` [PATCH 1/5] rename anon_vma_lock to vma_lock_anon_vma Rik van Riel
2010-05-26 19:38   ` Rik van Riel
2010-05-26 20:33   ` Larry Woodman
2010-05-26 20:33     ` Larry Woodman
2010-05-27 13:44   ` Minchan Kim
2010-05-27 13:44     ` Minchan Kim
2010-05-26 19:39 ` [PATCH 2/5] change direct call of spin_lock(anon_vma->lock) to inline function Rik van Riel
2010-05-26 19:39   ` Rik van Riel
2010-05-26 20:33   ` Larry Woodman
2010-05-26 20:33     ` Larry Woodman
2010-05-27 13:46   ` Minchan Kim
2010-05-27 13:46     ` Minchan Kim
2010-06-01 22:04   ` Andrew Morton
2010-06-01 22:04     ` Andrew Morton
2010-06-02  8:27     ` Peter Zijlstra
2010-06-02  8:27       ` Peter Zijlstra
2010-05-26 19:40 ` [PATCH 3/5] track the root (oldest) anon_vma Rik van Riel
2010-05-26 19:40   ` Rik van Riel
2010-05-26 20:34   ` Larry Woodman
2010-05-26 20:34     ` Larry Woodman
2010-05-27 13:48   ` Minchan Kim
2010-05-27 13:48     ` Minchan Kim
2010-05-26 19:40 ` [PATCH 4/5] always lock " Rik van Riel
2010-05-26 19:40   ` Rik van Riel
2010-05-26 20:36   ` Larry Woodman
2010-05-26 20:36     ` Larry Woodman
2010-05-27  0:57   ` KAMEZAWA Hiroyuki
2010-05-27  0:57     ` KAMEZAWA Hiroyuki
2010-05-27 13:55   ` Minchan Kim [this message]
2010-05-27 13:55     ` Minchan Kim
2010-05-27 17:48   ` Mel Gorman
2010-05-27 17:48     ` Mel Gorman
2010-05-26 19:41 ` [PATCH 5/5] extend KSM refcounts to the anon_vma root Rik van Riel
2010-05-26 19:41   ` Rik van Riel
2010-05-26 20:47   ` Larry Woodman
2010-05-26 20:47     ` Larry Woodman
2010-05-27 14:02   ` Minchan Kim
2010-05-27 14:02     ` Minchan Kim
2010-05-27 14:09     ` Rik van Riel
2010-05-27 14:09       ` Rik van Riel
2010-05-27 14:31   ` Minchan Kim
2010-05-27 14:31     ` Minchan Kim
2010-05-27 17:50   ` Mel Gorman
2010-05-27 17:50     ` Mel Gorman
  -- strict thread matches above, loose matches on Subject: below --
2010-05-12 17:38 [PATCH 0/5] always lock the root anon_vma Rik van Riel
2010-05-12 17:40 ` [PATCH 4/5] always lock the root (oldest) anon_vma Rik van Riel
2010-05-12 17:40   ` Rik van Riel
2010-05-12 21:02   ` Mel Gorman
2010-05-12 21:02     ` Mel Gorman
2010-05-12 21:08     ` Rik van Riel
2010-05-12 21:08       ` Rik van Riel
2010-05-13  9:54       ` Mel Gorman
2010-05-13  9:54         ` Mel Gorman
2010-05-13 14:33         ` [PATCH -v2 " Rik van Riel
2010-05-13 21:09           ` Andrew Morton
2010-05-26  4:00             ` Rik van Riel
2010-05-26 15:24               ` [PATCH -v2 0/5] always lock the root anon_vma Rik van Riel
2010-05-26 15:27                 ` [PATCH 4/5] always lock the root (oldest) anon_vma Rik van Riel
2010-05-26 15:27                   ` Rik van Riel
2010-05-12 21:55   ` Linus Torvalds
2010-05-12 21:55     ` Linus Torvalds
2010-05-12 22:18     ` Rik van Riel
2010-05-12 22:18       ` Rik van Riel
2010-05-12 22:26       ` Linus Torvalds
2010-05-12 22:26         ` Linus Torvalds

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=20100527135356.GD2112@barrios-desktop \
    --to=minchan.kim@gmail.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=riel@redhat.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.