From: Simon Jeons <simon.jeons@gmail.com>
To: Petr Holasek <pholasek@redhat.com>
Cc: Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Izik Eidus <izik.eidus@ravellosystems.com>,
Rik van Riel <riel@redhat.com>,
David Rientjes <rientjes@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH v7 1/2] KSM: numa awareness sysfs knob
Date: Mon, 07 Jan 2013 19:40:27 -0600 [thread overview]
Message-ID: <1357609227.4105.3.camel@kernel.cn.ibm.com> (raw)
In-Reply-To: <20130103122416.GB2277@thinkpad-work.redhat.com>
On Thu, 2013-01-03 at 13:24 +0100, Petr Holasek wrote:
> Hi Simon,
>
> On Mon, 31 Dec 2012, Simon Jeons wrote:
> > On Fri, 2012-12-28 at 02:32 +0100, Petr Holasek wrote:
> > >
> > > v7: - added sysfs ABI documentation for KSM
> >
> > Hi Petr,
> >
> > How you handle "memory corruption because the ksm page still points to
> > the stable_node that has been freed" mentioned by Andrea this time?
> >
>
Hi Petr,
You still didn't answer my question mentioned above. :)
> <snip>
>
> > >
> > > + /*
> > > + * If tree_page has been migrated to another NUMA node, it
> > > + * will be flushed out and put into the right unstable tree
> > > + * next time: only merge with it if merge_across_nodes.
> >
> > Why? Do you mean swap based migration? Or where I miss ....?
> >
>
> It can be physical page migration triggered by page compaction, memory hotplug
> or some NUMA sched/memory balancing algorithm developed recently.
>
> > > + * Just notice, we don't have similar problem for PageKsm
> > > + * because their migration is disabled now. (62b61f611e)
> > > + */
>
> Migration of KSM pages is disabled now, you can look into ^^^ commit and
> changes introduced to migrate.c.
>
> > > + if (!ksm_merge_across_nodes && page_to_nid(tree_page) != nid) {
> > > + put_page(tree_page);
> > > + return NULL;
> > > + }
> > > +
> > > ret = memcmp_pages(page, tree_page);
>
> </snip>
--
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:[~2013-01-08 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 3:22 [PATCH v6] KSM: numa awareness sysfs knob Petr Holasek
2012-12-24 5:08 ` Greg KH
2012-12-28 1:32 ` [PATCH v7 1/2] " Petr Holasek
2012-12-28 1:32 ` [PATCH v7 2/2] Documentation: add sysfs ABI documentation for ksm Petr Holasek
2013-01-01 4:41 ` [PATCH v7 1/2] KSM: numa awareness sysfs knob Simon Jeons
2013-01-03 12:24 ` Petr Holasek
2013-01-08 1:40 ` Simon Jeons [this message]
2013-01-08 2:46 ` Hugh Dickins
2013-01-01 8:46 ` Simon Jeons
2013-01-03 5:10 ` Hugh Dickins
2013-01-04 0:24 ` Simon Jeons
2013-01-04 23:03 ` Hugh Dickins
2013-01-05 0:30 ` Simon Jeons
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=1357609227.4105.3.camel@kernel.cn.ibm.com \
--to=simon.jeons@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anton@redhat.com \
--cc=hughd@google.com \
--cc=izik.eidus@ravellosystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pholasek@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).