From: Petr Holasek <pholasek@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] ksm: make rmap walks more scalable
Date: Fri, 21 Dec 2012 01:36:49 +0100 [thread overview]
Message-ID: <20121221003648.GA9649@thinkpad-work.redhat.com> (raw)
In-Reply-To: <50D3947F.2060503@oracle.com>
On Thu, 20 Dec 2012, Sasha Levin wrote:
> On 12/20/2012 05:37 PM, Hugh Dickins wrote:
> > On Thu, 20 Dec 2012, Sasha Levin wrote:
> >> On 12/19/2012 08:44 PM, 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>
> >>> ---
> >>
> >> Hi Hugh,
> >>
> >> This patch didn't fix the ksm oopses I'm seeing.
> >
> > I wouldn't expect it to (and should certainly have mentioned oopses
> > in the commit message if I'd intended): this patch was merely an
> > optimization/clarification of a commit gone in for 3.8-rc1.
> >
> > Understandable misunderstanding: you took my Cc too seriously,
> > I just thought I'd better keep Petr in the loop on current changes
> > to ksm.c, and foolishly kept you in too ;)
> >
> > Your oopses are on linux-next, which as of 20121220 still had Petr's
> > nice but buggy NUMA KSM patch in: it should go away when Stephen gets
> > a fresh mm update from Andrew, then reappear once his v6 goes into mm.
> >
> > To stop these oopses in get_mergeable_page (inlined in
> > unstable_tree_search_insert) you need the patch I showed on
> > Tuesday, which I hope he'll merge in for his v6. That doesn't fix
> > all of the problems, but hopefully all that you'll encounter before
> > I've devised a fix for the separate stale stable_nodes issue.
>
> My bad! I thought that this is the finalized version of the patch from
> Tuesday and was surprised when the oops was still there :)
>
> fwiw I'll use this to report that I'm not seeing any unexpected behaviour
> with this patch applied.
>
>
> Thanks,
> Sasha
>
Hugh, big thanks for your Tuesday fix, I am not able to reproduce reported
oops any more. I will continue with testing overnight and submit v6 version
tomorrow if there won't be any problem.
Should I also add [PATCH] ksm: make rmap walks more scalable into v6 or
can I rely on it?
thanks,
Petr H
--
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: Petr Holasek <pholasek@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] ksm: make rmap walks more scalable
Date: Fri, 21 Dec 2012 01:36:49 +0100 [thread overview]
Message-ID: <20121221003648.GA9649@thinkpad-work.redhat.com> (raw)
In-Reply-To: <50D3947F.2060503@oracle.com>
On Thu, 20 Dec 2012, Sasha Levin wrote:
> On 12/20/2012 05:37 PM, Hugh Dickins wrote:
> > On Thu, 20 Dec 2012, Sasha Levin wrote:
> >> On 12/19/2012 08:44 PM, 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>
> >>> ---
> >>
> >> Hi Hugh,
> >>
> >> This patch didn't fix the ksm oopses I'm seeing.
> >
> > I wouldn't expect it to (and should certainly have mentioned oopses
> > in the commit message if I'd intended): this patch was merely an
> > optimization/clarification of a commit gone in for 3.8-rc1.
> >
> > Understandable misunderstanding: you took my Cc too seriously,
> > I just thought I'd better keep Petr in the loop on current changes
> > to ksm.c, and foolishly kept you in too ;)
> >
> > Your oopses are on linux-next, which as of 20121220 still had Petr's
> > nice but buggy NUMA KSM patch in: it should go away when Stephen gets
> > a fresh mm update from Andrew, then reappear once his v6 goes into mm.
> >
> > To stop these oopses in get_mergeable_page (inlined in
> > unstable_tree_search_insert) you need the patch I showed on
> > Tuesday, which I hope he'll merge in for his v6. That doesn't fix
> > all of the problems, but hopefully all that you'll encounter before
> > I've devised a fix for the separate stale stable_nodes issue.
>
> My bad! I thought that this is the finalized version of the patch from
> Tuesday and was surprised when the oops was still there :)
>
> fwiw I'll use this to report that I'm not seeing any unexpected behaviour
> with this patch applied.
>
>
> Thanks,
> Sasha
>
Hugh, big thanks for your Tuesday fix, I am not able to reproduce reported
oops any more. I will continue with testing overnight and submit v6 version
tomorrow if there won't be any problem.
Should I also add [PATCH] ksm: make rmap walks more scalable into v6 or
can I rely on it?
thanks,
Petr H
next prev parent reply other threads:[~2012-12-21 0:36 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
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 [this message]
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=20121221003648.GA9649@thinkpad-work.redhat.com \
--to=pholasek@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--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.