From: Josef Bacik <josef@toxicpanda.com>
To: Boris Burkov <boris@bur.io>, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH RFC] btrfs: change commit txn to end txn in subvol_setflags ioctl
Date: Wed, 26 Aug 2020 10:23:27 -0400 [thread overview]
Message-ID: <c2c5399a-dd71-4285-2f09-adea1e1e6fa7@toxicpanda.com> (raw)
In-Reply-To: <20200804175516.2511704-1-boris@bur.io>
On 8/4/20 1:55 PM, Boris Burkov wrote:
> Currently, btrfs_ioctl_subvol_setflags forces a btrfs_commit_transaction
> while holding subvol_sem. As a result, we have seen workloads where
> calling `btrfs property set -ts <subvol> ro false` hangs waiting for a
> legitimately slow commit. This gets even worse if the workload tries to
> set flags on multiple subvolumes and the ioctls pile up on subvol_sem.
>
> Change the commit to a btrfs_end_transaction so that the ioctl can
> return in a timely fashion and piggy back on a later commit.
>
> Signed-off-by: Boris Burkov <boris@bur.io>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
I think we follow up with a btrfs-progs patch to make syncing an option with
setflags (or hell do it by default and make the option to not sync). Having the
commit here was arbitrary and not needed. Thanks,
Josef
prev parent reply other threads:[~2020-08-26 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 17:55 [PATCH RFC] btrfs: change commit txn to end txn in subvol_setflags ioctl Boris Burkov
2020-08-04 22:48 ` Qu Wenruo
2020-08-04 23:08 ` Josef Bacik
2020-08-05 13:40 ` Martin Raiber
2020-08-07 20:45 ` Boris Burkov
2020-08-10 18:05 ` Martin Raiber
2020-08-25 20:23 ` Boris Burkov
2020-08-26 14:23 ` Josef Bacik [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=c2c5399a-dd71-4285-2f09-adea1e1e6fa7@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dsterba@suse.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