From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>, Mel Gorman <mel@csn.ul.ie>
Subject: [PATCH 0/2] Reduce the amount of time spent in watermark-related functions V4
Date: Thu, 28 Oct 2010 16:13:34 +0100 [thread overview]
Message-ID: <1288278816-32667-1-git-send-email-mel@csn.ul.ie> (raw)
Changelog since V3
o Added Reviewed-bys
o Added comment on why pressure_threshold is what it is
o Make sure pressure threshold does not get over 125
o Call get_online_cpus and put_online_cpus as appropriate
The following two patches are in response to a bug report by Shaohua Li
where the amount of time spent in zone_nr_free_pages() is unacceptable
for large machines. All the background is in the first patches leader. The
second patch replaces two setter functions with one function that takes a
callback function as a parameter.
include/linux/mmzone.h | 10 ++------
include/linux/vmstat.h | 7 ++++++
mm/mmzone.c | 21 ------------------
mm/page_alloc.c | 35 ++++++++++++++++++++++++-------
mm/vmscan.c | 25 +++++++++++++--------
mm/vmstat.c | 54 +++++++++++++++++++++++++++++++++++++++++++++--
6 files changed, 103 insertions(+), 49 deletions(-)
Mel Gorman (2):
mm: page allocator: Adjust the per-cpu counter threshold when memory
is low
mm: vmstat: Use a single setter function and callback for adjusting
percpu thresholds
include/linux/mmzone.h | 10 ++------
include/linux/vmstat.h | 7 ++++++
mm/mmzone.c | 21 -------------------
mm/page_alloc.c | 35 ++++++++++++++++++++++++-------
mm/vmscan.c | 25 +++++++++++++---------
mm/vmstat.c | 52 +++++++++++++++++++++++++++++++++++++++++++++--
6 files changed, 101 insertions(+), 49 deletions(-)
--
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 reply other threads:[~2010-10-28 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 15:13 Mel Gorman [this message]
2010-10-28 15:13 ` [PATCH 1/2] mm: page allocator: Adjust the per-cpu counter threshold when memory is low Mel Gorman
2010-10-28 22:04 ` Andrew Morton
2010-10-29 10:12 ` Mel Gorman
2010-10-29 19:40 ` Andrew Morton
2010-11-02 0:53 ` Shaohua Li
2010-11-09 11:33 ` Mel Gorman
2010-11-09 16:48 ` Christoph Lameter
2010-10-29 14:58 ` Christoph Lameter
2010-10-29 18:25 ` Andrew Morton
2010-10-29 19:33 ` Christoph Lameter
2010-10-28 15:13 ` [PATCH 2/2] mm: vmstat: Use a single setter function and callback for adjusting percpu thresholds Mel Gorman
2010-10-28 22:09 ` Andrew Morton
2010-10-29 10:17 ` 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=1288278816-32667-1-git-send-email-mel@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=shaohua.li@intel.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).