From: Andrea Righi <righi.andrea@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kamezawa.hiroyu@jp.fujitsu.com, rientjes@google.com,
balbir@linux.vnet.ibm.com, mrubin@google.com, menage@google.com,
dave@linux.vnet.ibm.com, chlunde@ping.uio.no, dpshah@google.com,
eric.rannaud@gmail.com, fernando@oss.ntt.co.jp,
agk@sourceware.org, m.innocenti@cineca.it,
s-uchida@ap.jp.nec.com, ryov@valinux.co.jp, matt@bluehost.com,
dradford@bluehost.com, kosaki.motohiro@jp.fujitsu.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
containers@lists.osdl.org
Subject: Re: [PATCH -mm] mm: fine-grained dirty_ratio_pcm and dirty_background_ratio_pcm (v2)
Date: Mon, 10 Nov 2008 23:03:13 +0100 [thread overview]
Message-ID: <4918AFA1.4000102@gmail.com> (raw)
In-Reply-To: <20081110131255.ce71ce60.akpm@linux-foundation.org>
On 2008-11-10 22:12, Andrew Morton wrote:
> On Mon, 10 Nov 2008 21:58:28 +0100
> Andrea Righi <righi.andrea@gmail.com> wrote:
>
>> The current granularity of 5% of dirtyable memory for dirty pages writeback is
>> too coarse for large memory machines and this will get worse as
>> memory-size/disk-speed ratio continues to increase.
>>
>> These large writebacks can be unpleasant for desktop or latency-sensitive
>> environments, where the time to complete each writeback can be perceived as a
>> lack of responsiveness by the whole system.
>>
>> Following there's a similar solution as discussed in [1], but a little
>> bit simplified in order to provide the same functionality (in particular
>> to avoid backward compatibility problems) and reduce the amount of code
>> needed to implement an in-kernel parser to handle percentages with
>> decimals digits.
>>
>> The kernel provides the following parameters:
>> - dirty_ratio, dirty_background_ratio in percentage (1 ... 100)
>> - dirty_ratio_pcm, dirty_background_ratio_pcm in units of percent mille (1 ... 100,000)
>
> hm, so how long until dirty_ratio_pcm becomes too coarse...
>
> What happened to the idea of specifying these in units of kilobytes?
The conclusion was that with units in KB requires much more complexity
to keep in sync the old dirty_ratio (and dirty_background_ratio)
interface with the new one.
The KB limit is a static value, the other depends on the dirtyable
memory. If we want to preserve the same behaviour we should do the
following:
- when dirty_ratio changes to x:
dirty_amount_in_bytes = x * dirtyable_memory / 100.
- when dirty_amount_in_bytes changes to x:
dirty_ratio = x / dirtyable_memory * 100
But anytime the dirtyable memory changes (as well as the total memory in
the system) we should update both values accordingly to preserve the
coherency between them.
I wonder if setting also PERCENT_PCM (that is 1% expressed in
fine-grained units) as a parameter could be a better long-term solution.
And also use another name for it, because in this case this would be not
a milli-percent value anymore.
-Andrea
--
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-11-10 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1221232192-13553-1-git-send-email-righi.andrea@gmail.com>
[not found] ` <20080912131816.e0cfac7a.akpm@linux-foundation.org>
[not found] ` <532480950809221641y3471267esff82a14be8056586@mail.gmail.com>
[not found] ` <48EB4236.1060100@linux.vnet.ibm.com>
[not found] ` <48EB851D.2030300@gmail.com>
[not found] ` <20081008101642.fcfb9186.kamezawa.hiroyu@jp.fujitsu.com>
[not found] ` <48ECB215.4040409@linux.vnet.ibm.com>
2008-10-09 15:29 ` [PATCH -mm] page-writeback: fine-grained dirty_ratio and dirty_background_ratio Andrea Righi
2008-10-10 0:41 ` KAMEZAWA Hiroyuki
2008-10-10 9:32 ` Andrea Righi
2008-10-10 13:13 ` Andrea Righi
2008-11-10 20:58 ` [PATCH -mm] mm: fine-grained dirty_ratio_pcm and dirty_background_ratio_pcm (v2) Andrea Righi
2008-11-10 21:12 ` Andrew Morton
2008-11-10 22:03 ` Andrea Righi [this message]
2008-11-10 22:12 ` Andrew Morton
2008-11-10 22:15 ` David Rientjes
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=4918AFA1.4000102@gmail.com \
--to=righi.andrea@gmail.com \
--cc=agk@sourceware.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=chlunde@ping.uio.no \
--cc=containers@lists.osdl.org \
--cc=dave@linux.vnet.ibm.com \
--cc=dpshah@google.com \
--cc=dradford@bluehost.com \
--cc=eric.rannaud@gmail.com \
--cc=fernando@oss.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.innocenti@cineca.it \
--cc=matt@bluehost.com \
--cc=menage@google.com \
--cc=mrubin@google.com \
--cc=rientjes@google.com \
--cc=ryov@valinux.co.jp \
--cc=s-uchida@ap.jp.nec.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