From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Rik van Riel <riel@redhat.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [RFC][PATCH] page reclaim throttle take2
Date: Wed, 27 Feb 2008 10:33:41 +0530 [thread overview]
Message-ID: <47C4EF2D.90508@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080227140221.424C.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> Hi
>
>>> I don't think so.
>>> all modern many cpu machine stand on NUMA.
>>> it mean following,
>>> - if cpu increases, then zone increases, too.
>>>
>>> if default value increase by #cpus, lock contension dramatically increase
>>> on large numa.
>>>
>>> Have I overlooked anything?
>>>
>> How about adding something like..
>> ==
>> CONFIG_SIMULTANEOUS_PAGE_RECLAIMERS
>> int
>> default 3
>> depends on DEBUG
>> help
>> This value determines the number of threads which can do page reclaim
>> in a zone simultaneously. If this is too big, performance under heavy memory
>> pressure will decrease.
>> If unsure, use default.
>> ==
>>
>> Then, you can get performance reports from people interested in this
>> feature in test cycle.
>
> hm, intersting.
> but sysctl parameter is more better, i think.
>
> OK, I'll add it at next post.
I think sysctl should be interesting. The config option provides good
documentation, but it is static in nature (requires reboot to change). I wish we
could have the best of both worlds.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Rik van Riel <riel@redhat.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [RFC][PATCH] page reclaim throttle take2
Date: Wed, 27 Feb 2008 10:33:41 +0530 [thread overview]
Message-ID: <47C4EF2D.90508@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080227140221.424C.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> Hi
>
>>> I don't think so.
>>> all modern many cpu machine stand on NUMA.
>>> it mean following,
>>> - if cpu increases, then zone increases, too.
>>>
>>> if default value increase by #cpus, lock contension dramatically increase
>>> on large numa.
>>>
>>> Have I overlooked anything?
>>>
>> How about adding something like..
>> ==
>> CONFIG_SIMULTANEOUS_PAGE_RECLAIMERS
>> int
>> default 3
>> depends on DEBUG
>> help
>> This value determines the number of threads which can do page reclaim
>> in a zone simultaneously. If this is too big, performance under heavy memory
>> pressure will decrease.
>> If unsure, use default.
>> ==
>>
>> Then, you can get performance reports from people interested in this
>> feature in test cycle.
>
> hm, intersting.
> but sysctl parameter is more better, i think.
>
> OK, I'll add it at next post.
I think sysctl should be interesting. The config option provides good
documentation, but it is static in nature (requires reboot to change). I wish we
could have the best of both worlds.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
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:[~2008-02-27 5:09 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 2:32 [RFC][PATCH] page reclaim throttle take2 KOSAKI Motohiro
2008-02-26 2:32 ` KOSAKI Motohiro
2008-02-26 21:18 ` Peter Zijlstra
2008-02-26 21:18 ` Peter Zijlstra
2008-02-27 0:50 ` KAMEZAWA Hiroyuki
2008-02-27 0:50 ` KAMEZAWA Hiroyuki
2008-02-27 4:26 ` KOSAKI Motohiro
2008-02-27 4:26 ` KOSAKI Motohiro
2008-02-27 4:27 ` Balbir Singh
2008-02-27 4:27 ` Balbir Singh
2008-02-27 4:45 ` KOSAKI Motohiro
2008-02-27 4:45 ` KOSAKI Motohiro
2008-02-27 5:00 ` KAMEZAWA Hiroyuki
2008-02-27 5:00 ` KAMEZAWA Hiroyuki
2008-02-27 5:04 ` KOSAKI Motohiro
2008-02-27 5:04 ` KOSAKI Motohiro
2008-02-27 5:03 ` Balbir Singh [this message]
2008-02-27 5:03 ` Balbir Singh
2008-02-27 5:13 ` KOSAKI Motohiro
2008-02-27 5:13 ` KOSAKI Motohiro
2008-02-27 5:19 ` David Rientjes
2008-02-27 5:19 ` David Rientjes
2008-02-27 5:33 ` KOSAKI Motohiro
2008-02-27 5:33 ` KOSAKI Motohiro
2008-02-27 5:47 ` David Rientjes
2008-02-27 5:47 ` David Rientjes
2008-02-27 5:48 ` Balbir Singh
2008-02-27 5:48 ` Balbir Singh
2008-02-27 6:09 ` David Rientjes
2008-02-27 6:09 ` David Rientjes
2008-02-27 7:10 ` KOSAKI Motohiro
2008-02-27 7:10 ` KOSAKI Motohiro
2008-02-27 7:19 ` David Rientjes
2008-02-27 7:19 ` David Rientjes
2008-02-27 7:51 ` KAMEZAWA Hiroyuki
2008-02-27 7:51 ` KAMEZAWA Hiroyuki
2008-02-27 7:56 ` David Rientjes
2008-02-27 7:56 ` David Rientjes
2008-02-27 8:09 ` KAMEZAWA Hiroyuki
2008-02-27 8:09 ` KAMEZAWA Hiroyuki
2008-02-27 15:30 ` Rik van Riel
2008-02-27 15:30 ` Rik van Riel
2008-02-27 7:59 ` Balbir Singh
2008-02-27 7:59 ` Balbir Singh
2008-02-27 8:47 ` David Rientjes
2008-02-27 8:47 ` David Rientjes
2008-02-27 9:01 ` Balbir Singh
2008-02-27 9:01 ` Balbir Singh
2008-02-27 9:44 ` Peter Zijlstra
2008-02-27 9:44 ` Peter Zijlstra
2008-02-27 6:52 ` KOSAKI Motohiro
2008-02-27 6:52 ` KOSAKI Motohiro
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=47C4EF2D.90508@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.