From: Wols Lists <antlists@youngman.org.uk>
To: Paul Lawrence <paullawrence@google.com>
Cc: dm-devel@redhat.com, Linux kernel <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: Re: [RFC] dm-bow working prototype
Date: Thu, 25 Oct 2018 22:15:39 +0100 [thread overview]
Message-ID: <5BD2327B.1040908@youngman.org.uk> (raw)
In-Reply-To: <d00e361b-b849-3139-7e7a-02f05f3794c3@google.com>
On 25/10/18 19:13, Paul Lawrence wrote:
>> I have some questions about dm-bow:
>> – How file system agnostic this feature is planned to be? While it is
>> designed with ext4 in mind, is it going to work when used over other
>> file systems, like FAT or BTRFS for example?
> So long as the file system supports fstrim, it should work. If the file
> system creates a lot of churn say by running garbage collection, I'd not
> recommend it. And I really don't see the use case if the file system has
> any sort of snapshot capability - that will always be a superior
> solution to a block level one IMO.
Sorry for being dense, but why is this posted to linux-raid, then? Raid
does not support fstrim, and is filesystem-agnostic.
I can imagine people here being interested, but it feels to me as though
your functionality is completely orthogonal to raid. Sorry.
Cheers,
Wol
next prev parent reply other threads:[~2018-10-25 21:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 21:23 Paul Lawrence
2018-10-23 22:18 ` Alasdair G Kergon
2018-10-24 18:42 ` Paul Lawrence
2018-10-24 19:24 ` [dm-devel] " Mikulas Patocka
2018-10-25 0:01 ` Alasdair G Kergon
2018-10-25 10:20 ` Bryn M. Reeves
2018-10-25 17:23 ` Paul Lawrence
2018-10-26 20:03 ` Mikulas Patocka
2018-10-29 16:51 ` Paul Lawrence
2018-11-15 23:15 ` Mikulas Patocka
2018-12-02 10:07 ` Sandeep Patil
2018-10-25 16:30 ` MegaBrutal
2018-10-25 18:13 ` Paul Lawrence
2018-10-25 21:15 ` Wols Lists [this message]
2018-10-25 21:43 ` [dm-devel] " Darrick J. Wong
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=5BD2327B.1040908@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=paullawrence@google.com \
--subject='Re: [RFC] dm-bow working prototype' \
/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
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).