linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Yunlei He <heyunlei@huawei.com>,
	jaegeuk@kernel.org, yuchao0@huawei.com,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/2] f2fs: let discard thread wait a little longer if dev is busy
Date: Sun, 8 Apr 2018 19:01:25 +0800	[thread overview]
Message-ID: <10980e48-287c-635b-8dd5-464c8fc76a7a@kernel.org> (raw)
In-Reply-To: <1523171471-538-2-git-send-email-heyunlei@huawei.com>

On 2018/4/8 15:11, Yunlei He wrote:
> This patch modify discard thread wait policy as below:
> 	issued       io_interrupted     wait time(ms)
> 1.        8                 0               50
> 2.      (0,8)               1               50
> 3.        0                 1              500 (dev is busy)
> 4.        0                 0            60000 (no candidates)
> 
> Signed-off-by: Yunlei He <heyunlei@huawei.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  reply	other threads:[~2018-04-08 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-08  7:11 [PATCH 1/2] f2fs: stop issue discard if something wrong with f2fs Yunlei He
2018-04-08  7:11 ` [PATCH 2/2] f2fs: let discard thread wait a little longer if dev is busy Yunlei He
2018-04-08 11:01   ` Chao Yu [this message]
2018-04-08  8:26 ` [PATCH 1/2] f2fs: stop issue discard if something wrong with f2fs Chao Yu
2018-04-08  9:19   ` heyunlei
2018-04-08 10:01     ` Chao Yu

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=10980e48-287c-635b-8dd5-464c8fc76a7a@kernel.org \
    --to=chao@kernel.org \
    --cc=heyunlei@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).