From: Andy Whitcroft <apw@canonical.com>
To: Sebastian Frias <sf84@laposte.net>
Cc: Joe Perches <joe@perches.com>, mason <slash.tmp@free.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [PATCH] mm: add config option to select the initial overcommit mode
Date: Tue, 10 May 2016 13:39:41 +0100 [thread overview]
Message-ID: <20160510123941.GB11368@brain> (raw)
In-Reply-To: <5731CD6F.9070101@laposte.net>
On Tue, May 10, 2016 at 02:00:47PM +0200, Sebastian Frias wrote:
> Hi,
>
> Using checkpatch.pl on the forwarded patch results in:
>
> WARNING: please write a paragraph that describes the config symbol fully
> #57: FILE: mm/Kconfig:451:
> + config OVERCOMMIT_GUESS
>
> WARNING: please write a paragraph that describes the config symbol fully
> #64: FILE: mm/Kconfig:458:
> + config OVERCOMMIT_ALWAYS
>
> but there is a 'help' section for those 'config' sections.
> NOTE: I followed the same indentation than the code laying just above the place where I inserted mine.
>
> I think it is a false positive, what do you think?
>
> Best regards,
>
> Sebastian
Well, I am expecting the issue to be that the per option help is not
indented within the option like I am expecting ...
> Date: Tue, 10 May 2016 13:56:30 +0200
> From: Sebastian Frias <sf84@laposte.net>
> To: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>, Michal
> Hocko <mhocko@suse.com>, Linus Torvalds <torvalds@linux-foundation.org>
> CC: LKML <linux-kernel@vger.kernel.org>, mason <slash.tmp@free.fr>
> Subject: [PATCH] mm: add config option to select the initial overcommit mode
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101
> Thunderbird/31.2.0
>
> Currently the initial value of the overcommit mode is OVERCOMMIT_GUESS.
> However, on embedded systems it is usually better to disable overcommit
> to avoid waking up the OOM-killer and its well known undesirable
> side-effects.
>
> This config option allows to setup the initial overcommit mode to any of
> the 3 available values, OVERCOMMIT_GUESS (which remains as default),
> OVERCOMMIT_ALWAYS and OVERCOMMIT_NEVER.
> The overcommit mode can still be changed thru sysctl after the system
> boots up.
>
> This config option depends on CONFIG_EXPERT.
> This patch does not introduces functional changes.
>
> Signed-off-by: Sebastian Frias <sf84@laposte.net>
> ---
>
> NOTE: I understand that the overcommit mode can be changed dynamically thru
> sysctl, but on embedded systems, where we know in advance that overcommit
> will be disabled, there's no reason to postpone such setting.
>
> I would also be interested in knowing if you guys think this option should
> disable sysctl access for overcommit mode, essentially hardcoding the
> overcommit mode when this option is used.
>
> NOTE2: I tried to track down the history of overcommit but back then there
> were no single patches apparently and the patch that appears to have
> introduced the first overcommit mode (OVERCOMMIT_ALWAYS) is commit
> 9334eab8a36f ("Import 2.1.27"). OVERCOMMIT_NEVER was introduced with commit
> 502bff0685b2 ("[PATCH] strict overcommit").
> My understanding is that prior to commit 9334eab8a36f ("Import 2.1.27")
> there was no overcommit, is that correct?
>
> NOTE3: checkpatch.pl is warning about missing description for the config
> symbols ("please write a paragraph that describes the config symbol fully")
> but my understanding is that that is a false positive (or the warning message
> not clear enough for me to understand it) considering that I have added
> 'help' sections for each 'config' section.
> ---
> mm/Kconfig | 32 ++++++++++++++++++++++++++++++++
> mm/util.c | 8 +++++++-
> 2 files changed, 39 insertions(+), 1 deletion(-)
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> index abb7dcf..6dad57d 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -439,6 +439,38 @@ choice
> benefit.
> endchoice
>
> +choice
> + prompt "Overcommit Mode"
> + default OVERCOMMIT_GUESS
> + depends on EXPERT
> + help
> + Selects the initial value for Overcommit mode.
> +
> + NOTE: The overcommit mode can be changed dynamically through sysctl.
> +
> + config OVERCOMMIT_GUESS
> + bool "Guess"
I am expecting the help below to be indented at the same level as the
bool above. As you have done with the help for the choice itself. I am
pretty sure checkpatch is assuming the "contents" of the config item are
all intented more than it is.
> + help
> + Selecting this option forces the initial value of overcommit mode to
> + "Guess" overcommits. This is the default value.
> + See Documentation/vm/overcommit-accounting for more information.
[...]
-apw
next prev parent reply other threads:[~2016-05-10 12:39 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 11:56 [PATCH] mm: add config option to select the initial overcommit mode Sebastian Frias
2016-05-10 12:00 ` Fwd: " Sebastian Frias
2016-05-10 12:39 ` Andy Whitcroft [this message]
2016-05-10 13:02 ` Sebastian Frias
2016-05-13 8:04 ` Michal Hocko
2016-05-13 8:44 ` Mason
2016-05-13 9:52 ` Sebastian Frias
2016-05-13 12:00 ` Michal Hocko
2016-05-13 12:39 ` Sebastian Frias
2016-05-13 13:11 ` Austin S. Hemmelgarn
2016-05-13 13:32 ` Sebastian Frias
2016-05-13 13:51 ` Austin S. Hemmelgarn
2016-05-13 14:35 ` Sebastian Frias
2016-05-13 14:54 ` Michal Hocko
2016-05-13 15:15 ` Austin S. Hemmelgarn
2016-05-13 13:34 ` Sebastian Frias
2016-05-13 14:14 ` Austin S. Hemmelgarn
2016-05-13 14:23 ` Sebastian Frias
2016-05-13 15:02 ` Austin S. Hemmelgarn
2016-05-13 15:01 ` One Thousand Gnomes
2016-05-13 15:15 ` Sebastian Frias
2016-05-13 15:25 ` Michal Hocko
2016-05-13 14:51 ` Michal Hocko
2016-05-13 14:59 ` Mason
2016-05-13 15:11 ` One Thousand Gnomes
2016-05-13 15:26 ` Michal Hocko
2016-05-13 15:32 ` Sebastian Frias
2016-05-13 15:10 ` Sebastian Frias
2016-05-13 15:41 ` One Thousand Gnomes
2016-05-23 13:11 ` Sebastian Frias
2016-05-13 9:52 ` Michal Hocko
2016-05-13 10:18 ` Mason
2016-05-13 10:42 ` Sebastian Frias
2016-05-13 11:44 ` Michal Hocko
2016-05-13 12:15 ` Mason
2016-05-13 14:01 ` Michal Hocko
2016-05-13 14:15 ` Sebastian Frias
2016-05-13 15:04 ` One Thousand Gnomes
2016-05-13 15:37 ` Sebastian Frias
2016-05-13 15:43 ` One Thousand Gnomes
2016-05-17 8:24 ` Sebastian Frias
2016-05-17 8:57 ` Michal Hocko
2016-05-17 16:16 ` Sebastian Frias
2016-05-17 17:29 ` Austin S. Hemmelgarn
2016-05-18 15:19 ` Sebastian Frias
2016-05-18 16:28 ` Austin S. Hemmelgarn
2016-05-17 20:16 ` Michal Hocko
2016-05-18 15:18 ` Sebastian Frias
2016-05-19 7:14 ` Michal Hocko
2016-05-13 17:01 ` Austin S. Hemmelgarn
2016-05-13 13:27 ` Austin S. Hemmelgarn
2016-05-17 9:03 ` Mason
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=20160510123941.GB11368@brain \
--to=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
/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