From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
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 09:57:57 +0530 [thread overview]
Message-ID: <47C4E6CD.6090401@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080227131939.4244.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> Hi Peter,
>
>>> +
>>> + atomic_t nr_reclaimers;
>>> + wait_queue_head_t reclaim_throttle_waitq;
>>> /*
>>> * rarely used fields:
>>> */
>> Small nit, that extra blank line seems at the wrong end of the text
>> block :-)
>
> Agghhh, sorry ;-)
> I'll fix at next post.
>
>>> +out:
>>> + atomic_dec(&zone->nr_reclaimers);
>>> + wake_up_all(&zone->reclaim_throttle_waitq);
>>> +
>>> + return ret;
>>> +}
>> Would it be possible - and worthwhile - to make this FIFO fair?
>
> Hmmm
> may be, we don't need perfectly fair.
> because try_to_free_page() is unfair mechanism.
>
> but I will test use wake_up() instead wake_up_all().
> it makes so so fair order if no performance regression happend.
>
> Thanks very useful comment.
One more thing, I would request you to add default heuristics (number of
reclaimers), based on the number of cpus in the system. Letting people tuning it
is fine, but defaults should be related to number of cpus, nodes and zones on
the system. Zones can be reaped in parallel per node and cpus allow threads to
run in parallel. So please use that to come up with good defaults, instead of a
number like "3".
--
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 4:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 2:32 KOSAKI Motohiro
2008-02-26 21:18 ` Peter Zijlstra
2008-02-27 0:50 ` KAMEZAWA Hiroyuki
2008-02-27 4:26 ` KOSAKI Motohiro
2008-02-27 4:27 ` Balbir Singh [this message]
2008-02-27 4:45 ` KOSAKI Motohiro
2008-02-27 5:00 ` KAMEZAWA Hiroyuki
2008-02-27 5:04 ` KOSAKI Motohiro
2008-02-27 5:03 ` Balbir Singh
2008-02-27 5:13 ` KOSAKI Motohiro
2008-02-27 5:19 ` David Rientjes
2008-02-27 5:33 ` KOSAKI Motohiro
2008-02-27 5:47 ` David Rientjes
2008-02-27 5:48 ` Balbir Singh
2008-02-27 6:09 ` David Rientjes
2008-02-27 7:10 ` KOSAKI Motohiro
2008-02-27 7:19 ` David Rientjes
2008-02-27 7:51 ` KAMEZAWA Hiroyuki
2008-02-27 7:56 ` David Rientjes
2008-02-27 8:09 ` KAMEZAWA Hiroyuki
2008-02-27 15:30 ` Rik van Riel
2008-02-27 7:59 ` Balbir Singh
2008-02-27 8:47 ` David Rientjes
2008-02-27 9:01 ` Balbir Singh
2008-02-27 9:44 ` Peter Zijlstra
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=47C4E6CD.6090401@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox