From: Nikolay Borisov <nborisov@suse.com>
To: Dominique Martinet <asmadeus@codewreck.org>, linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com,
Dominique Martinet <dominique.martinet@atmark-techno.com>
Subject: Re: [RFC PATCH] btrfs-progs: prop: add datacow inode property
Date: Tue, 5 Apr 2022 17:21:06 +0300 [thread overview]
Message-ID: <85af4827-0a21-80d4-5d60-43e0e398a4e2@suse.com> (raw)
In-Reply-To: <YkPuYyoV6LRWJdbS@codewreck.org>
On 30.03.22 г. 8:45 ч., Dominique Martinet wrote:
>
> I appreciate it's a trifling feature, but I'd appreciate not having to
> teach our users about chattr if they could only have to manipulate btrfs
> properties so I'd appreciate some feedback!:)
>
> If you just say 'no' I'll bite the bullet and install e2fsprogs just for
> btrfs and document the command, but as things stand my users (embedded
> device developpers) have no way of disabling cow for e.g. database
> workloads and that's not really good long-term.
Just my 2 cents: I think we should strive to rely as much as possible on
the generic infrastructure where we can. The nocow options is one such
case. The way I see it btrfs property is used to manage features which
are indeed specific to btrfs and have no generic alternative.
What's more I don't see how 'chattr +C /some/path' can be considered
'complex' to teach someone, plus chattr is a standard linux utility.
next prev parent reply other threads:[~2022-04-05 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 4:22 [RFC PATCH] btrfs-progs: prop: add datacow inode property Dominique Martinet
2022-03-30 5:45 ` Dominique Martinet
2022-04-05 14:21 ` Nikolay Borisov [this message]
2022-04-05 22:35 ` Dominique Martinet
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=85af4827-0a21-80d4-5d60-43e0e398a4e2@suse.com \
--to=nborisov@suse.com \
--cc=asmadeus@codewreck.org \
--cc=dominique.martinet@atmark-techno.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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