From: Yafang Shao <laoar.shao@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mhocko@suse.com, Johannes Weiner <hannes@cmpxchg.org>,
vdavydov.dev@gmail.com, jlayton@redhat.com, nborisov@suse.com,
Theodore Ts'o <tytso@mit.edu>,
mawilcox@microsoft.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH] mm/page-writeback.c: fix bug caused by disable periodic writeback
Date: Mon, 9 Oct 2017 18:44:23 +0800 [thread overview]
Message-ID: <CALOAHbAS_DyhOarH0ZEBWfmB_3wvEV2WA_k_UzUe7b+QRAQ=6A@mail.gmail.com> (raw)
2017-10-09 17:56 GMT+08:00 Jan Kara <jack@suse.cz>:
> On Sat 07-10-17 06:58:04, Yafang Shao wrote:
>> After disable periodic writeback by writing 0 to
>> dirty_writeback_centisecs, the handler wb_workfn() will not be
>> entered again until the dirty background limit reaches or
>> sync syscall is executed or no enough free memory available or
>> vmscan is triggered.
>> So the periodic writeback can't be enabled by writing a non-zero
>> value to dirty_writeback_centisecs
>> As it can be disabled by sysctl, it should be able to enable by
>> sysctl as well.
>>
>> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
>> ---
>> mm/page-writeback.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
>> index 0b9c5cb..e202f37 100644
>> --- a/mm/page-writeback.c
>> +++ b/mm/page-writeback.c
>> @@ -1972,7 +1972,13 @@ bool wb_over_bg_thresh(struct bdi_writeback *wb)
>> int dirty_writeback_centisecs_handler(struct ctl_table *table, int write,
>> void __user *buffer, size_t *length, loff_t *ppos)
>> {
>> - proc_dointvec(table, write, buffer, length, ppos);
>> + unsigned int old_interval = dirty_writeback_interval;
>> + int ret;
>> +
>> + ret = proc_dointvec(table, write, buffer, length, ppos);
>> + if (!ret && !old_interval && dirty_writeback_interval)
>> + wakeup_flusher_threads(0, WB_REASON_PERIODIC);
>> +
>
> I agree it is good to schedule some writeback. However Jens has some
> changes queued in linux-block tree in this area so your change won't apply.
> So please base your changes on his tree.
>
Do you mean this tree
git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git ?
I have checked his tree and find nothing need to change on my patch.
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
Thanks
Yafang
--
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 reply other threads:[~2017-10-09 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 10:44 Yafang Shao [this message]
2017-10-09 11:03 ` Jan Kara
2017-10-09 11:36 ` Yafang Shao
-- strict thread matches above, loose matches on Subject: below --
2017-10-06 22:58 Yafang Shao
2017-10-09 9:56 ` Jan Kara
2017-10-09 22:42 ` Andrew Morton
2017-10-10 8:00 ` Yafang Shao
2017-10-10 8:48 ` Jan Kara
2017-10-10 9:14 ` Yafang Shao
2017-10-10 9:33 ` Jan Kara
2017-10-11 4:06 ` Yafang Shao
2017-10-10 8:45 ` 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='CALOAHbAS_DyhOarH0ZEBWfmB_3wvEV2WA_k_UzUe7b+QRAQ=6A@mail.gmail.com' \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=mhocko@suse.com \
--cc=nborisov@suse.com \
--cc=tytso@mit.edu \
--cc=vdavydov.dev@gmail.com \
/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