From: Andrew Morton <akpm@linux-foundation.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH v4] mm: introduce validity check on vm dirtiness settings
Date: Tue, 26 Sep 2017 19:54:09 -0700 [thread overview]
Message-ID: <20170926195409.0867d13620e1219ca6676821@linux-foundation.org> (raw)
In-Reply-To: <CALOAHbB2CTfjAWgazxdAQTiOjCZFHF8Cn2mXv=kFe3prp_zg-A@mail.gmail.com>
On Wed, 27 Sep 2017 09:38:21 +0800 Yafang Shao <laoar.shao@gmail.com> wrote:
> > And existing scripts which do not do this will cease to work correctly,
> > no?
> >
>
> The existing scritpts won't work correctly. That's also what I have
> worried before.
>
> But under this condition, there's a error message generated by "sysctl
> -w" to tell them the first setting was failure.
> This error message may be a reminder to them that there are some
> connections between background and direct limit, and should not set
> arbitrary.
> May that's better. I'm not sure.
Maybe we can leave the logic as-is and simply print a warning when an
illogical state exists.
--
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:[~2017-09-27 2:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 23:12 Yafang Shao
2017-09-26 23:59 ` Andrew Morton
2017-09-27 1:38 ` Yafang Shao
2017-09-27 2:54 ` Andrew Morton [this message]
2017-09-27 4:14 ` Yafang Shao
2017-09-27 19:33 ` Andrew Morton
2017-09-28 1:27 ` Yafang Shao
2017-09-29 1:19 ` [lkp-robot] [mm] d33dff8a27: autotest.linus_stress.fail kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2017-09-21 13:59 [PATCH v4] mm: introduce validity check on vm dirtiness settings Yafang Shao
2017-09-21 11:52 ` Jan Kara
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=20170926195409.0867d13620e1219ca6676821@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
/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