All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: David Rientjes <rientjes@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	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 14:31:44 +0530	[thread overview]
Message-ID: <47C526F8.8010807@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0802270045400.31372@chino.kir.corp.google.com>

David Rientjes wrote:
> On Wed, 27 Feb 2008, Balbir Singh wrote:
> 
>> Let's forget node hotplug for the moment, but what if someone
>>
>> 1. Changes the machine configuration and adds more nodes, do we expect the
>> kernel to be recompiled? Or is it easier to update /etc/sysctl.conf?
>> 2. Uses fake NUMA nodes and increases/decreases the number of nodes across
>> reboots. Should the kernel be recompiled?
>>
> 
> That is why the proposal was made to make this a static configuration 
> option, such as CONFIG_NUM_RECLAIM_THREADS_PER_NODE, that will handle both 
> situations.
> 

You mentioned CONFIG_NUM_RECLAIM_THREADS_PER_CPU and not
CONFIG_NUM_RECLAIM_THREADS_PER_NODE. The advantage with syscalls is that even if
we get the thing wrong, the system administrator has an alternative. Please look
through the existing sysctl's and you'll see what I mean. What is wrong with
providing the flexibility that comes with sysctl? We cannot possibly think of
all situations and come up with the right answer for a heuristic. Why not come
up with a default and let everyone use what works for them?


-- 
	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: David Rientjes <rientjes@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	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 14:31:44 +0530	[thread overview]
Message-ID: <47C526F8.8010807@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0802270045400.31372@chino.kir.corp.google.com>

David Rientjes wrote:
> On Wed, 27 Feb 2008, Balbir Singh wrote:
> 
>> Let's forget node hotplug for the moment, but what if someone
>>
>> 1. Changes the machine configuration and adds more nodes, do we expect the
>> kernel to be recompiled? Or is it easier to update /etc/sysctl.conf?
>> 2. Uses fake NUMA nodes and increases/decreases the number of nodes across
>> reboots. Should the kernel be recompiled?
>>
> 
> That is why the proposal was made to make this a static configuration 
> option, such as CONFIG_NUM_RECLAIM_THREADS_PER_NODE, that will handle both 
> situations.
> 

You mentioned CONFIG_NUM_RECLAIM_THREADS_PER_CPU and not
CONFIG_NUM_RECLAIM_THREADS_PER_NODE. The advantage with syscalls is that even if
we get the thing wrong, the system administrator has an alternative. Please look
through the existing sysctl's and you'll see what I mean. What is wrong with
providing the flexibility that comes with sysctl? We cannot possibly think of
all situations and come up with the right answer for a heuristic. Why not come
up with a default and let everyone use what works for them?


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

  reply	other threads:[~2008-02-27  9:06 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
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 [this message]
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=47C526F8.8010807@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 \
    --cc=rientjes@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 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.