From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f71.google.com (mail-it0-f71.google.com [209.85.214.71]) by kanga.kvack.org (Postfix) with ESMTP id 4E3666B0038 for ; Tue, 26 Sep 2017 07:45:47 -0400 (EDT) Received: by mail-it0-f71.google.com with SMTP id 85so13612687ith.0 for ; Tue, 26 Sep 2017 04:45:47 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id h135sor3550466ioe.13.2017.09.26.04.45.46 for (Google Transport Security); Tue, 26 Sep 2017 04:45:46 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20170926112656.tbu7nr2lxdqt5rft@dhcp22.suse.cz> References: <1505861015-11919-1-git-send-email-laoar.shao@gmail.com> <20170926102532.culqxb45xwzafomj@dhcp22.suse.cz> <20170926112656.tbu7nr2lxdqt5rft@dhcp22.suse.cz> From: Yafang Shao Date: Tue, 26 Sep 2017 19:45:45 +0800 Message-ID: Subject: Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Jan Kara , akpm@linux-foundation.org, Johannes Weiner , vdavydov.dev@gmail.com, jlayton@redhat.com, nborisov@suse.com, Theodore Ts'o , mawilcox@microsoft.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org 2017-09-26 19:26 GMT+08:00 Michal Hocko : > On Tue 26-09-17 19:06:37, Yafang Shao wrote: >> 2017-09-26 18:25 GMT+08:00 Michal Hocko : >> > On Wed 20-09-17 06:43:35, Yafang Shao wrote: >> >> we can find the logic in domain_dirty_limits() that >> >> when dirty bg_thresh is bigger than dirty thresh, >> >> bg_thresh will be set as thresh * 1 / 2. >> >> if (bg_thresh >= thresh) >> >> bg_thresh = thresh / 2; >> >> >> >> But actually we can set vm background dirtiness bigger than >> >> vm dirtiness successfully. This behavior may mislead us. >> >> We'd better do this validity check at the beginning. >> > >> > This is an admin only interface. You can screw setting this up even >> > when you keep consistency between the background and direct limits. In >> > general we do not try to be clever for these knobs because we _expect_ >> > admins to do sane things. Why is this any different and why do we need >> > to add quite some code to handle one particular corner case? >> > >> >> Of course we expect admins to do the sane things, but not all admins >> are expert or faimilar with linux kernel source code. >> If we have to read the source code to know what is the right thing to >> do, I don't think this is a good interface, even for the admin. > > Well, it is kind of natural to setup background below the direct limit > in general so I am not sure what is so surprising here. Moreover setting > a non default drity limits already requires some expertise. It is not > like an arbitrary value will work just fine... > >> Anyway, there's no document on that direct limits should not less than >> background limits. > > Then improve the documentation. I have improved the kernel documentation as well, in order to make it more clear for the newbies. >> > To be honest I am not entirely sure this is worth the code and the >> > future maintenance burden. >> I'm not sure if this code is a burden for the future maintenance, but >> I think that if we don't introduce this code it is a burden to the >> admins. > > anytime we might need to tweak background vs direct limit we would have > to change these checks as well and that sounds like a maint. burden to > me. Would pls. show me some example ? > -- > Michal Hocko > SUSE Labs -- 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: email@kvack.org