public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: David Disseldorp <ddiss@suse.de>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC] btrfs: reflink: disable cross-subvolume clone/dedupe for simple quota
Date: Fri, 22 Mar 2024 06:47:09 +1030	[thread overview]
Message-ID: <88553d8e-81fd-4fe1-bd3d-d5244de162ba@gmx.com> (raw)
In-Reply-To: <20240322002544.6904f696@echidna>



在 2024/3/21 23:55, David Disseldorp 写道:
> On Thu, 21 Mar 2024 14:09:38 +1030, Qu Wenruo wrote:
> ...
>> [REASON FOR RFC]
>> I'm not sure how important the cross-subvolume clone functionality is in
>> real-world.
>>
>> But considering squota is mostly designed for container usage, in that
>> case disabling cross-subvolume clone should be completely fine.
>
> I think copy_file_range() is reasonably common nowadays, and this would
> impact such workloads. I don't find the creator-subvol-pays simple quota
> behaviour too confusing, so would vote too keep things as is.
>
> Cheers, David
>
OK, thanks for all the feedback.

Please drop this patch.

Thanks,
Qu

  reply	other threads:[~2024-03-21 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21  3:39 [PATCH RFC] btrfs: reflink: disable cross-subvolume clone/dedupe for simple quota Qu Wenruo
2024-03-21  7:34 ` Roman Mamedov
2024-03-21 13:25 ` David Disseldorp
2024-03-21 20:17   ` Qu Wenruo [this message]
2024-03-21 18:51 ` Josef Bacik
2024-03-21 19:08   ` Boris Burkov
2024-03-21 23:59     ` Qu Wenruo

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=88553d8e-81fd-4fe1-bd3d-d5244de162ba@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=ddiss@suse.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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