linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Damian Tometzki <damian.tometzki@icloud.com>,
	Yafang Shao <laoar.shao@gmail.com>
Cc: akpm@linux-foundation.org, jack@suse.cz, hannes@cmpxchg.org,
	vdavydov.dev@gmail.com, jlayton@redhat.com, nborisov@suse.com,
	tytso@mit.edu, yamada.masahiro@socionext.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH for linux-next] mm/page-writeback.c: make changes of dirty_writeback_centisecs take effect immediately
Date: Sat, 14 Oct 2017 14:19:34 -0600	[thread overview]
Message-ID: <b088d7e7-bda9-186d-9334-12f16aa92463@kernel.dk> (raw)
In-Reply-To: <20171014175906.GA1825@zrhn9910b>

On 10/14/2017 11:59 AM, Damian Tometzki wrote:
> On Sat, 14. Oct 16:38, Yafang Shao wrote:
>> This patch is the followup of the prvious patch:
>> [writeback: schedule periodic writeback with sysctl].
>>
>> There's another issue to fix.
>> For example,
>> - When the tunable was set to one hour and is reset to one second, the
>>   new setting will not take effect for up to one hour.
>>
>> Kicking the flusher threads immediately fixes it.
>>
>> Cc: Jens Axboe <axboe@kernel.dk>
>> Cc: Jan Kara <jack@suse.cz>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
>> ---
>>  mm/page-writeback.c | 11 ++++++++++-
>>  1 file changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
>> index 3969e69..768fe4e 100644
>> --- a/mm/page-writeback.c
>> +++ b/mm/page-writeback.c
>> @@ -1978,7 +1978,16 @@ int dirty_writeback_centisecs_handler(struct ctl_table *table, int write,
>>  	int ret;
>>  
>>  	ret = proc_dointvec(table, write, buffer, length, ppos);
>> -	if (!ret && !old_interval && dirty_writeback_interval)
>> +
>> +	/*
>> +	 * Writing 0 to dirty_writeback_interval will disable periodic writeback
>> +	 * and a different non-zero value will wakeup the writeback threads.
>> +	 * wb_wakeup_delayed() would be more appropriate, but it's a pain to
>> +	 * iterate over all bdis and wbs.
>> +	 * The reason we do this is to make the change take effect immediately.
>> +	 */
>> +	if (!ret && write && dirty_writeback_interval &&
>> +		dirty_writeback_interval != old_interval)
>>  		wakeup_flusher_threads(WB_REASON_PERIODIC);
> Is that call right ? The call need two arguments ?
> --> wakeup_flusher_threads(0,WB_REASON_PERIODIC);

It's right, the nr_pages argument was killed.

-- 
Jens Axboe

--
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>

      reply	other threads:[~2017-10-14 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14  8:38 Yafang Shao
2017-10-14 15:14 ` Jens Axboe
2017-10-14 17:59 ` Damian Tometzki
2017-10-14 20:19   ` Jens Axboe [this message]

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=b088d7e7-bda9-186d-9334-12f16aa92463@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=damian.tometzki@icloud.com \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=jlayton@redhat.com \
    --cc=laoar.shao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nborisov@suse.com \
    --cc=tytso@mit.edu \
    --cc=vdavydov.dev@gmail.com \
    --cc=yamada.masahiro@socionext.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