From: David Sterba <dsterba@suse.cz>
To: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Cc: dsterba@suse.cz, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] btrfs: don't commit transaction for every subvol create
Date: Fri, 21 Apr 2023 17:23:23 +0200 [thread overview]
Message-ID: <20230421152323.GA19619@twin.jikos.cz> (raw)
In-Reply-To: <9472eb7d-9daa-54c0-2d33-740edf509542@dorminy.me>
On Fri, Apr 21, 2023 at 08:58:54AM -0400, Sweet Tea Dorminy wrote:
>
> >
> > So I think it's safe and allows the use case of creating many subvolumes
> > without the full transaction commit overhead. And we don't need the
> > commandline options. Added to misc-next, thanks.
>
> Just to check, have you pushed misc-next containing this to github? I
> can't find it in git log.
Maybe I forgot to push the latest changes, now pushed.
prev parent reply other threads:[~2023-04-21 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 19:10 [PATCH] btrfs: don't commit transaction for every subvol create Sweet Tea Dorminy
2023-04-12 1:45 ` Neal Gompa
2023-04-12 2:34 ` Qu Wenruo
2023-04-12 2:35 ` Qu Wenruo
2023-04-12 13:49 ` Josef Bacik
2023-04-12 2:29 ` Qu Wenruo
2023-04-12 13:51 ` Josef Bacik
2023-04-12 22:35 ` Neal Gompa
2023-04-17 18:46 ` David Sterba
2023-04-21 12:58 ` Sweet Tea Dorminy
2023-04-21 15:23 ` David Sterba [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=20230421152323.GA19619@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
/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