linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Wu, Fengguang" <fengguang.wu@intel.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"riel@redhat.com" <riel@redhat.com>
Subject: Re: [PATCH]vmscan: handle underflow for get_scan_ratio
Date: Mon, 12 Apr 2010 09:57:39 +0800	[thread overview]
Message-ID: <20100412015739.GA14988@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20100409142057.be0ce5af.akpm@linux-foundation.org>

On Sat, Apr 10, 2010 at 05:20:57AM +0800, Andrew Morton wrote:
> On Fri, 9 Apr 2010 14:51:04 +0800
> Shaohua Li <shaohua.li@intel.com> wrote:
> 
> > get_scan_ratio() calculates percentage and if the percentage is < 1%, it will
> > round percentage down to 0% and cause we completely ignore scanning anon/file
> > pages to reclaim memory even the total anon/file pages are very big.
> > 
> > To avoid underflow, we don't use percentage, instead we directly calculate
> > how many pages should be scaned. In this way, we should get several scanned pages
> > for < 1% percent.
> > 
> > This has some benefits:
> > 1. increase our calculation precision
> > 2. making our scan more smoothly. Without this, if percent[x] is underflow,
> > shrink_zone() doesn't scan any pages and suddenly it scans all pages when priority
> > is zero. With this, even priority isn't zero, shrink_zone() gets chance to scan
> > some pages.
> > 
> > Note, this patch doesn't really change logics, but just increase precision. For
> > system with a lot of memory, this might slightly changes behavior. For example,
> > in a sequential file read workload, without the patch, we don't swap any anon
> > pages. With it, if anon memory size is bigger than 16G, we will see one anon page
> > swapped. The 16G is calculated as PAGE_SIZE * priority(4096) * (fp/ap). fp/ap
> > is assumed to be 1024 which is common in this workload. So the impact sounds not
> > a big deal.
> 
> I grabbed this.
> 
> Did we decide that this needed to be backported into 2.6.33.x?  If so,
> some words explaining the reasoning would be needed.
> 
> Come to that, it's not obvious that we need this in 2.6.34 either. 
Not needed.

> is the user-visible impact here?
Should be very small I think.

Thanks,
Shaohua

--
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>

  parent reply	other threads:[~2010-04-12  2:01 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  5:53 Shaohua Li
2010-03-30  6:08 ` KOSAKI Motohiro
2010-03-30  6:32   ` Shaohua Li
2010-03-30  6:40     ` KOSAKI Motohiro
2010-03-30  6:53       ` Shaohua Li
2010-03-30  7:31         ` KOSAKI Motohiro
2010-03-30  8:13           ` Shaohua Li
2010-03-31  4:53   ` Shaohua Li
2010-03-31  5:38     ` KOSAKI Motohiro
2010-03-31  5:51       ` Wu Fengguang
2010-03-31  6:00         ` KOSAKI Motohiro
2010-03-31  6:03           ` Wu Fengguang
2010-04-01 22:16           ` Andrew Morton
2010-04-02  9:13             ` KOSAKI Motohiro
2010-04-06  1:22               ` Wu Fengguang
2010-04-06  3:36               ` Rik van Riel
2010-03-31  5:53       ` KOSAKI Motohiro
2010-04-02  6:50         ` Shaohua Li
2010-04-02  9:14           ` KOSAKI Motohiro
2010-04-02  9:24             ` Shaohua Li
2010-04-04 14:19               ` KOSAKI Motohiro
2010-04-06  1:25                 ` Shaohua Li
2010-04-06  1:36                   ` KOSAKI Motohiro
2010-04-06  1:50                   ` Wu Fengguang
2010-04-06  2:06                     ` KOSAKI Motohiro
2010-04-06  2:30                       ` Wu Fengguang
2010-04-06  2:58                         ` KOSAKI Motohiro
2010-04-06  3:31                           ` Wu Fengguang
2010-04-06  3:40                             ` Rik van Riel
2010-04-06  4:49                               ` Wu Fengguang
2010-04-06  5:09                                 ` Shaohua Li
2010-04-04  0:48           ` Wu Fengguang
2010-04-06  1:27             ` Shaohua Li
2010-04-06  5:03           ` Wu Fengguang
2010-04-06  5:36             ` Shaohua Li
2010-04-09  6:51             ` Shaohua Li
2010-04-09 21:20               ` Andrew Morton
2010-04-09 21:25                 ` Rik van Riel
2010-04-13  1:30                   ` KOSAKI Motohiro
2010-04-13  2:42                     ` Rik van Riel
2010-04-13  7:55                       ` KOSAKI Motohiro
2010-04-13  8:55                         ` KOSAKI Motohiro
2010-04-14  1:27                           ` Shaohua Li
2010-04-15  3:25                             ` KOSAKI Motohiro
2010-04-12  1:57                 ` Shaohua Li [this message]
2010-03-31  5:41     ` Wu Fengguang
2010-03-30 10:17 ` Minchan Kim
2010-03-30 10:25   ` KOSAKI Motohiro
2010-03-30 11:56 ` Balbir Singh

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=20100412015739.GA14988@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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