From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: kosaki.motohiro@jp.fujitsu.com, Neil Brown <neilb@suse.de>,
Con Kolivas <kernel@kolivas.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"riel@redhat.com" <riel@redhat.com>,
"david@fromorbit.com" <david@fromorbit.com>,
"hch@lst.de" <hch@lst.de>, "axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [PATCH] writeback: remove the internal 5% low bound on dirty_ratio
Date: Tue, 24 Aug 2010 09:00:51 +0900 (JST) [thread overview]
Message-ID: <20100824085812.F3AD.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20100823062359.GA19586@localhost>
> writeback: remove the internal 5% low bound on dirty_ratio
>
> The dirty_ratio was silently limited in global_dirty_limits() to >= 5%. This
> is not a user expected behavior. And it's inconsistent with calc_period_shift(),
> which uses the plain vm_dirty_ratio value. So let's rip the internal bound.
>
> At the same time, force a user visible low bound of 1% for the vm.dirty_ratio
> interface. Applications trying to write 0 will be rejected with -EINVAL. This
> will break user space applications if they
> 1) try to write 0 to vm.dirty_ratio
> 2) and check the return value
> That is very weird combination, so the risk of breaking user space is low.
I'm ok this one too. because I bet nobody use 0% dirty ratio on their production
server and/or their own desktop. (i.e. I don't mind lab machine crash)
Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>
> CC: Jan Kara <jack@suse.cz>
> CC: Neil Brown <neilb@suse.de>
> CC: Rik van Riel <riel@redhat.com>
> CC: Con Kolivas <kernel@kolivas.org>
> CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> kernel/sysctl.c | 2 +-
> mm/page-writeback.c | 10 ++--------
> 2 files changed, 3 insertions(+), 9 deletions(-)
>
> --- linux-next.orig/mm/page-writeback.c 2010-08-20 20:14:11.000000000 +0800
> +++ linux-next/mm/page-writeback.c 2010-08-23 10:31:01.000000000 +0800
> @@ -415,14 +415,8 @@ void global_dirty_limits(unsigned long *
>
> if (vm_dirty_bytes)
> dirty = DIV_ROUND_UP(vm_dirty_bytes, PAGE_SIZE);
> - else {
> - int dirty_ratio;
> -
> - dirty_ratio = vm_dirty_ratio;
> - if (dirty_ratio < 5)
> - dirty_ratio = 5;
> - dirty = (dirty_ratio * available_memory) / 100;
> - }
> + else
> + dirty = (vm_dirty_ratio * available_memory) / 100;
>
> if (dirty_background_bytes)
> background = DIV_ROUND_UP(dirty_background_bytes, PAGE_SIZE);
> --- linux-next.orig/kernel/sysctl.c 2010-08-23 14:06:11.000000000 +0800
> +++ linux-next/kernel/sysctl.c 2010-08-23 14:07:30.000000000 +0800
> @@ -1029,7 +1029,7 @@ static struct ctl_table vm_table[] = {
> .maxlen = sizeof(vm_dirty_ratio),
> .mode = 0644,
> .proc_handler = dirty_ratio_handler,
> - .extra1 = &zero,
> + .extra1 = &one,
> .extra2 = &one_hundred,
> },
> {
--
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:[~2010-08-24 0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 3:25 Wu Fengguang
2010-08-20 3:46 ` Rik van Riel
2010-08-20 4:13 ` KOSAKI Motohiro
2010-08-20 5:50 ` Con Kolivas
2010-08-20 5:56 ` Wu Fengguang
2010-08-23 4:42 ` Neil Brown
2010-08-23 6:23 ` Wu Fengguang
2010-08-23 6:30 ` Con Kolivas
2010-08-23 7:15 ` Wu Fengguang
2010-08-24 0:00 ` KOSAKI Motohiro [this message]
[not found] ` <201008241620.54048.kernel@kolivas.org>
[not found] ` <20100824071440.GA14598@localhost>
[not found] ` <201008251840.00532.kernel@kolivas.org>
2010-08-26 1:29 ` Wu Fengguang
2010-08-26 1:36 ` Neil Brown
2010-08-26 4:22 ` KOSAKI Motohiro
2010-08-27 10:36 Wu Fengguang
2010-08-27 10:39 ` Peter Zijlstra
2010-08-27 13:47 ` Rik van Riel
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=20100824085812.F3AD.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@lst.de \
--cc=kernel@kolivas.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=neilb@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