|From:||Linus Torvalds <torvalds-AT-linux-foundation.org>|
|To:||"Artem S. Tashkinov" <t.artem-AT-lycos.com>|
|Subject:||Re: Disabling in-memory write cache for x86-64 in Linux II|
|Date:||Fri, 25 Oct 2013 09:43:36 +0100|
|Cc:||Wu Fengguang <fengguang.wu-AT-intel.com>, Andrew Morton <akpm-AT-linux-foundation.org>, Linux Kernel Mailing List <linux-kernel-AT-vger.kernel.org>|
On Fri, Oct 25, 2013 at 9:30 AM, Artem S. Tashkinov <email@example.com> wrote: > > My feeling is that vm.dirty_ratio/vm.dirty_background_ratio should _not_ be > percentage based, 'cause for PCs/servers with a lot of memory (say 64GB or > more) this value becomes unrealistic (13GB) and I've already had some > unpleasant effects due to it. Right. The percentage notion really goes back to the days when we typically had 8-64 *megabytes* of memory So if you had a 8MB machine you wouldn't want to have more than one megabyte of dirty data, but if you were "Mr Moneybags" and could afford 64MB, you might want to have up to 8MB dirty!! Things have changed. So I would suggest we change the defaults. Or pwehaps make the rule be that "the ratio numbers are 'ratio of memory up to 1GB'", to make the semantics similar across 32-bit HIGHMEM machines and 64-bit machines. The modern way of expressing the dirty limits are to give the actual absolute byte amounts, but we default to the legacy ratio mode.. Linus
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds