linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
	YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
	lizf@cn.fujitsu.com, Rik van Riel <riel@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH 4/4] Memory controller soft limit reclaim on contention (v5)
Date: Fri, 13 Mar 2009 16:17:25 +0900 (JST)	[thread overview]
Message-ID: <20090313160632.683D.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090313070340.GI16897@balbir.in.ibm.com>

> > hm
> > I read past discussion. so, I think we discuss many aspect at once.
> > So, my current thinking is below, 
> > 
> > (1) if the group don't have any soft limit shrinking page, 
> >     mem_cgroup_soft_limit_reclaim() spent time unnecessary.
> >     -> right.
> 
> If the soft limit RB tree is empty, we don't spend any time at all.
> Are you referring to something else? Am I missing something? The tree
> will be empty if no group is over the soft limit.

maybe, I am missing anything.
May I ask your following paragraph meaning?


> I experimented a *lot* with zone reclaim and found it to be not so
> effective. Here is why
> 
> 1. We have no control over priority or how much to scan, that is
> controlled by balance_pgdat(). If we find that we are unable to scan
> anything, we continue scanning with the scan > 0 check, but we scan
> the same pages and the same number, because shrink_zone does scan >>
> priority.

I thought this sentense mean soft-limit-shrinking spent a lot of time.
if not, could you please tell me what makes so slower?

and, you wrote:

> 
> Yes, I sent that reason out as comments to Kame's patches. kswapd or
> balance_pgdat controls the zones, priority and in effect how many
> pages we scan while doing reclaim. I did lots of experiments and found
> that if soft limit reclaim occurred from kswapd, soft_limit_reclaim
> would almost always fail and shrink_zone() would succeed, since it
> looks at the whole zone and is always able to find some pages at all
> priority levels. It also does not allow for targetted reclaim based on
> how much we exceed the soft limit by. 

but, if "soft_limit_reclaim fail and shrink_zone() succeed" don't cause
any performance degression, I don't find why kswapd is wrong.

I guess you and kamezawa-san know it detail. but my understanding don't reach it.
Could you please tell me what so slowness.



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

  reply	other threads:[~2009-03-13  7:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 17:56 [PATCH 0/4] Memory controller soft limit patches (v5) Balbir Singh
2009-03-12 17:56 ` [PATCH 1/4] Memory controller soft limit documentation (v5) Balbir Singh
2009-03-12 17:56 ` [PATCH 2/4] Memory controller soft limit interface (v5) Balbir Singh
2009-03-12 22:59   ` Andrew Morton
2009-03-13  4:58     ` Balbir Singh
2009-03-12 17:56 ` [PATCH 3/4] Memory controller soft limit organize cgroups (v5) Balbir Singh
2009-03-12 23:04   ` Andrew Morton
2009-03-13  5:03     ` Balbir Singh
2009-03-13  0:47   ` KOSAKI Motohiro
2009-03-13  5:04     ` Balbir Singh
2009-03-13  5:22       ` KOSAKI Motohiro
2009-03-13  8:20         ` Balbir Singh
2009-03-13  6:59   ` KAMEZAWA Hiroyuki
2009-03-13  7:09     ` Balbir Singh
2009-03-12 17:56 ` [PATCH 4/4] Memory controller soft limit reclaim on contention (v5) Balbir Singh
2009-03-12 23:34   ` Andrew Morton
2009-03-13  7:53     ` Balbir Singh
2009-03-13  1:36   ` KOSAKI Motohiro
2009-03-13  4:13     ` Balbir Singh
2009-03-13  4:31       ` KOSAKI Motohiro
2009-03-13  4:50         ` KOSAKI Motohiro
2009-03-13  5:07           ` Balbir Singh
2009-03-13  6:54             ` KOSAKI Motohiro
2009-03-13  7:03               ` Balbir Singh
2009-03-13  7:17                 ` KOSAKI Motohiro [this message]
2009-03-13  7:26                   ` Balbir Singh
2009-03-13  8:37                     ` KAMEZAWA Hiroyuki
2009-03-13  5:26           ` Balbir Singh
2009-03-13  5:34             ` KOSAKI Motohiro
2009-03-13  4:58         ` Balbir Singh
2009-03-13  6:51   ` KAMEZAWA Hiroyuki
2009-03-13  7:15     ` Balbir Singh
2009-03-13  8:41       ` KAMEZAWA Hiroyuki
2009-03-13  7:02 ` [PATCH 0/4] Memory controller soft limit patches (v5) KAMEZAWA Hiroyuki
2009-03-13  7:07   ` KAMEZAWA Hiroyuki
2009-03-13  7:15     ` Andrew Morton
2009-03-13  7:29       ` Balbir Singh
2009-03-13  7:18     ` 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=20090313160632.683D.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=riel@redhat.com \
    --cc=yamamoto@valinux.co.jp \
    /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