Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: don't update the block group item if used bytes are the same
Date: Fri, 2 Sep 2022 14:51:28 +0200	[thread overview]
Message-ID: <20220902125127.GX13489@twin.jikos.cz> (raw)
In-Reply-To: <20220818122624.GJ13489@twin.jikos.cz>

On Thu, Aug 18, 2022 at 02:26:24PM +0200, David Sterba wrote:
> On Mon, Jul 11, 2022 at 04:47:25PM +0800, Qu Wenruo wrote:
> > No need to completely cancel each other.
> > 
> > In fact, just COWing a path without adding/deleting new cousins would be
> > enough, and that would be very common for a lot of tree block operations.
> 
> I would be interested in numbers too, a percentage of skip/total would
> be good for some workloads so we have at least some idea.

I'll keep the patch in for-next until we see some numbers about how much
the optimization is used.

  reply	other threads:[~2022-09-02 13:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  6:37 [PATCH] btrfs: don't update the block group item if used bytes are the same Qu Wenruo
2022-07-11  8:30 ` Nikolay Borisov
2022-07-11  8:47   ` Qu Wenruo
2022-08-18 12:26     ` David Sterba
2022-09-02 12:51       ` David Sterba [this message]
2022-09-07 14:31 ` Josef Bacik
2022-09-07 17:29   ` Josef Bacik
2022-09-07 22:08     ` David Sterba
2022-09-07 22:20     ` Qu Wenruo
2022-09-07 22:35       ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2022-09-09  6:45 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=20220902125127.GX13489@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=quwenruo.btrfs@gmx.com \
    --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