From: Vlad <vovan@vovan.nl>
To: linux-bcache@vger.kernel.org
Subject: Re: block size question
Date: Wed, 18 May 2016 18:24:45 +0200 [thread overview]
Message-ID: <573C974D.3040008@net.home> (raw)
In-Reply-To: <573C8E6E.8030008@megasoft.be>
Killian,
Thanks for your help! I think it's the best to reformat both bcache
devices with block size of 4k in my case where cached device has block
size of 512 and backing device 4k.
Regards,
Vlad.
On 18/05/16 17:46, Killian De Volder wrote:
> Done some testing for you:
> The -B --block size has to be a a power2 of -C --block size.
>
> (Note: all information is about bcache1 not bcachefs if that is what you are talking about)
>
> Killian De Volder
>
>
> On 18-05-16 07:50, Vlad wrote:
>> Hallo,
>>
>> What would be the optimal block size in case if physical block sizes
>> different for cache and backing devices? Can I use different block sizes
>> for cache and backing devices, like:
>> make-bcache --block 4k -B /dev/sdc
>> make-bcache --block 512 -C /dev/sda
>>
>> I have a feeling that the block size should be the same and the biggest
>> block size should be used, but I'd appreciate any thoughts about that.
>>
>> Thanks in advance,
>> Vlad.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-05-18 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 5:50 block size question Vlad
2016-05-18 7:11 ` Killian De Volder
2016-05-18 14:14 ` Killian De Volder
2016-05-18 15:46 ` Killian De Volder
2016-05-18 16:24 ` Vlad [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=573C974D.3040008@net.home \
--to=vovan@vovan.nl \
--cc=linux-bcache@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).