[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20100824085812.F3AD.A69D9226@jp.fujitsu.com>
Date: Tue, 24 Aug 2010 09:00:51 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Wu Fengguang <fengguang.wu@...el.com>
Cc: kosaki.motohiro@...fujitsu.com, Neil Brown <neilb@...e.de>,
Con Kolivas <kernel@...ivas.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"riel@...hat.com" <riel@...hat.com>,
"david@...morbit.com" <david@...morbit.com>,
"hch@....de" <hch@....de>, "axboe@...nel.dk" <axboe@...nel.dk>
Subject: Re: [PATCH] writeback: remove the internal 5% low bound on dirty_ratio
> 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@...fujitsu.com>
>
> CC: Jan Kara <jack@...e.cz>
> CC: Neil Brown <neilb@...e.de>
> CC: Rik van Riel <riel@...hat.com>
> CC: Con Kolivas <kernel@...ivas.org>
> CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> CC: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@...el.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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists