Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 6.11
Date: Thu, 18 Jul 2024 15:37:02 +0200	[thread overview]
Message-ID: <20240718133701.GG8022@twin.jikos.cz> (raw)
In-Reply-To: <CAHk-=wgw9uyrpi+qL28Ee650p7jaXEMjUoRzXBymraoENDMt6w@mail.gmail.com>

On Wed, Jul 17, 2024 at 01:21:17PM -0700, Linus Torvalds wrote:
> On Mon, 15 Jul 2024 at 11:12, David Sterba <dsterba@suse.com> wrote:
> >
> > There's a merge conflict caused by the latency fixes from last week in
> > extent_map.c:btrfs_scan_inode(), related commits 4e660ca3a98d931809734
> > and b3ebb9b7e92a928344a. Resolved in branch for-6.11-merged and that's
> > been in linux-next for a few days.
> 
> Oh, and I notice that my resolution is slightly different, but looks
> like the actual code is equivalent.
> 
> I kept the "q" logic that had been introduced by commit 4e660ca3a98d
> ("btrfs: use a regular rb_root instead of cached rb_root for
> extent_map_tree").
> 
> I don't know how you prefer the code, but it kept the two "while
> (node)" loops in that file looking similar.

That is fine, keeping the same style makes sense.

> Of course, they were very different in other respects (ie
> drop_all_extent_maps_fast() does all extents unconditionally with that
> retry logic, while btrfs_scan_inode() has that whole "bail out on any
> contention" model, so whatever.
> 
> Anyway, it all *looks* ok to me, but please go and double-check that I
> didn't mess something up.

Looks correct to me as well.

  reply	other threads:[~2024-07-18 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 18:12 [GIT PULL] Btrfs updates for 6.11 David Sterba
2024-07-17 20:18 ` pr-tracker-bot
2024-07-17 20:21 ` Linus Torvalds
2024-07-18 13:37   ` David Sterba [this message]
2024-07-19 11:25 ` Geert Uytterhoeven
2024-07-19 11:35   ` Geert Uytterhoeven
2024-07-19 13:42     ` David Sterba

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=20240718133701.GG8022@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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