From: David Rientjes <rientjes@google.com>
To: Ying Han <yinghan@google.com>
Cc: Satoru Moriya <satoru.moriya@hds.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Randy Dunlap <rdunlap@xenotime.net>,
dle-develop@lists.sourceforge.net,
Seiji Aguchi <seiji.aguchi@hds.com>
Subject: Re: [RFC][PATCH 0/2] Tunable watermark
Date: Fri, 7 Jan 2011 14:39:21 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1101071436220.23858@chino.kir.corp.google.com> (raw)
In-Reply-To: <AANLkTikQPXWkEJwN5fV2vnUS37Fs+GNzFXuFkKXcnzmu@mail.gmail.com>
On Fri, 7 Jan 2011, Ying Han wrote:
> On the other hand, having the low/high wmark consider more characters
> other than the
> size of the zone sounds useful.
The semantics of any watermark is to trigger events to happen at a
specific level, so they should be static with respect to a frame of
reference (which in the VM case is the min watermark with respect to the
size of the zone). If you're going to adjust the min watermark, it's then
_mandatory_ to adjust the others to that frame of reference, you shouldn't
need to tune them independently.
The problem that Satoru is reporting probably has nothing to do with the
watermarks themselves but probably requires more aggressive action by
kswapd and/or memory compaction.
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-07 22:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 22:03 Satoru Moriya
2011-01-07 22:04 ` [RFC][PATCH 1/2] Add explanation about min_free_kbytes to clarify its effect Satoru Moriya
2011-01-07 22:27 ` David Rientjes
2011-01-07 22:07 ` [RFC][PATCH 2/2] Make watermarks tunable separately Satoru Moriya
2011-01-07 22:23 ` [RFC][PATCH 0/2] Tunable watermark David Rientjes
2011-01-07 22:35 ` Ying Han
2011-01-07 22:39 ` David Rientjes [this message]
2011-01-13 22:05 ` Satoru Moriya
2011-01-13 22:24 ` David Rientjes
2011-01-13 22:05 ` Satoru Moriya
2011-01-13 22:20 ` David Rientjes
2011-01-21 0:16 ` Rik van Riel
2011-02-10 18:30 ` Satoru Moriya
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.1101071436220.23858@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=dle-develop@lists.sourceforge.net \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=rdunlap@xenotime.net \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=yinghan@google.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