All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lyle <mlyle@lyle.org>
To: tang.junhui@zte.com.cn, colyli@suse.de
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] [PATCH v2] bcache: segregate flash only volume write streams from cached devices
Date: Mon, 4 Dec 2017 23:17:04 -0800	[thread overview]
Message-ID: <b7474776-7126-2d7d-43e4-f956b66d1fdb@lyle.org> (raw)
In-Reply-To: <1512367914-9257-1-git-send-email-tang.junhui@zte.com.cn>

Tang Junhui--

Hi

On 12/03/2017 10:11 PM, tang.junhui@zte.com.cn wrote:
> From: Tang Junhui <tang.junhui@zte.com.cn>
> 
> Hello Mike & Coly
> 
> Could you please have a reveiw for this patch?
> 
>> From: Tang Junhui <tang.junhui@zte.com.cn>
>>
>> In such scenario that there are some flash only volumes
>> , and some cached devices, when many tasks request these devices in
>> writeback mode, the write IOs may fall to the same bucket as bellow:
>> | cached data | flash data | cached data | cached data| flash data|
>> then after writeback of these cached devices, the bucket would
>> be like bellow bucket:
>> | free | flash data | free | free | flash data |
>>
>> So, there are many free space in this bucket, but since data of flash
>> only volumes still exists, so this bucket cannot be reclaimable,
>> which would cause waste of bucket space.
>>
>> In this patch, we segregate flash only volume write streams from
>> cached devices, so data from flash only volumes and cached devices
>> can store in different buckets.
>>
>> Compare to v1 patch, this patch do not add a additionally open bucket
>> list, and it is try best to segregate flash only volume write streams
>> from cached devices, sectors of flash only volumes may still be mixed
>> with dirty sectors of cached device, but the number is very small.
>>
>> Signed-off-by: Tang Junhui <tang.junhui@zte.com.cn>

LGTM, and I have added to my staging tree, though it required
cleanpatch. (executable, line ending).

Thanks,

Mike

  reply	other threads:[~2017-12-05  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04  6:11 [PATCH] [PATCH v2] bcache: segregate flash only volume write streams from cached devices tang.junhui
2017-12-05  7:17 ` Michael Lyle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-22  5:52 tang.junhui
2017-11-22  3:25 tang.junhui
2017-11-22  4:53 ` Michael Lyle

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=b7474776-7126-2d7d-43e4-f956b66d1fdb@lyle.org \
    --to=mlyle@lyle.org \
    --cc=colyli@suse.de \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=tang.junhui@zte.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.