From: Mel Gorman <mgorman@suse.de>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Petr Holasek <pholasek@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] ksm: make rmap walks more scalable
Date: Thu, 20 Dec 2012 11:17:43 +0000 [thread overview]
Message-ID: <20121220111743.GF10819@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1212191742440.25409@eggly.anvils>
On Wed, Dec 19, 2012 at 05:44:29PM -0800, Hugh Dickins wrote:
> The rmap walks in ksm.c are like those in rmap.c:
> they can safely be done with anon_vma_lock_read().
>
> Signed-off-by: Hugh Dickins <hughd@google.com>
Acked-by: Mel Gorman <mgorman@suse.de>
I'm assuming these are going to go through Andrew's tree as normal for
-mm patches. Andrew?
--
Mel Gorman
SUSE Labs
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Petr Holasek <pholasek@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] ksm: make rmap walks more scalable
Date: Thu, 20 Dec 2012 11:17:43 +0000 [thread overview]
Message-ID: <20121220111743.GF10819@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1212191742440.25409@eggly.anvils>
On Wed, Dec 19, 2012 at 05:44:29PM -0800, Hugh Dickins wrote:
> The rmap walks in ksm.c are like those in rmap.c:
> they can safely be done with anon_vma_lock_read().
>
> Signed-off-by: Hugh Dickins <hughd@google.com>
Acked-by: Mel Gorman <mgorman@suse.de>
I'm assuming these are going to go through Andrew's tree as normal for
-mm patches. Andrew?
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-12-20 11:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 1:42 [PATCH] sched: numa: ksm: fix oops in task_numa_placment() Hugh Dickins
2012-12-20 1:42 ` Hugh Dickins
2012-12-20 1:44 ` [PATCH] ksm: make rmap walks more scalable Hugh Dickins
2012-12-20 1:44 ` Hugh Dickins
2012-12-20 11:17 ` Mel Gorman [this message]
2012-12-20 11:17 ` Mel Gorman
2012-12-20 21:49 ` Sasha Levin
2012-12-20 21:49 ` Sasha Levin
2012-12-20 22:26 ` Linus Torvalds
2012-12-20 22:26 ` Linus Torvalds
2012-12-20 22:40 ` Hugh Dickins
2012-12-20 22:40 ` Hugh Dickins
2012-12-20 22:37 ` Hugh Dickins
2012-12-20 22:37 ` Hugh Dickins
2012-12-20 22:43 ` Sasha Levin
2012-12-20 22:43 ` Sasha Levin
2012-12-21 0:36 ` Petr Holasek
2012-12-21 0:36 ` Petr Holasek
2012-12-21 2:35 ` Hugh Dickins
2012-12-21 2:35 ` Hugh Dickins
2012-12-20 11:14 ` [PATCH] sched: numa: ksm: fix oops in task_numa_placment() Mel Gorman
2012-12-20 11:14 ` Mel Gorman
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=20121220111743.GF10819@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=pholasek@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.org \
/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.