From: David Rientjes <rientjes@google.com>
To: Petr Holasek <pholasek@redhat.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Chris Wright <chrisw@sous-sol.org>,
Izik Eidus <izik.eidus@ravellosystems.com>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Anton Arapov <anton@redhat.com>
Subject: Re: [PATCH v2] KSM: numa awareness sysfs knob
Date: Mon, 2 Jul 2012 14:26:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1207021425110.24806@chino.kir.corp.google.com> (raw)
In-Reply-To: <20120630114053.GA3036@stainedmachine.redhat.com>
On Sat, 30 Jun 2012, Petr Holasek wrote:
> The problem of the first patch/RFC was that merging algorithm was unstable
> and could merge pages with distance higher than was set up (described by
> Nai Xia in RFC thread [1]). Sure, this instability could be solved, but for
> ksm pages shared by many other pages on different nodes we would have to still
> recalculate which page is "in the middle" and in case of change migrate it
> between nodes every time when ksmd reach new shareable page or when some
> sharing page is removed.
>
Or you could simply refuse to ever merge any page that is identical to a
page on a node with a distance greater than the threshold, i.e. never
merge pages even under the threshold if a page exists on a node higher
than the threshold.
--
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:[~2012-07-02 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 11:49 Petr Holasek
2012-06-29 13:03 ` Cong Wang
2012-06-29 13:23 ` Petr Holasek
2012-06-29 16:05 ` Johannes Weiner
2012-06-29 16:30 ` Petr Holasek
2012-06-29 16:47 ` Johannes Weiner
2012-06-29 22:30 ` David Rientjes
2012-06-30 11:40 ` Petr Holasek
2012-07-02 21:26 ` David Rientjes [this message]
2012-07-03 17:02 ` Petr Holasek
2012-06-29 21:17 ` Andrew Morton
2012-06-29 22:50 ` David Rientjes
2012-06-30 9:43 ` Izik Eidus
2012-06-30 12:29 ` Petr Holasek
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.DEB.2.00.1207021425110.24806@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anton@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=hannes@cmpxchg.org \
--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 \
/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