public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: accessors: delete token versions of set/get helpers
Date: Mon, 30 Jun 2025 18:11:59 +0200	[thread overview]
Message-ID: <20250630161159.GI31241@twin.jikos.cz> (raw)
In-Reply-To: <8993e49a-7fc2-41a0-8dec-3dbbf84ec601@gmx.com>

On Sun, Jun 29, 2025 at 10:43:26AM +0930, Qu Wenruo wrote:
> 
> 
> 在 2025/6/27 23:33, David Sterba 写道:
> > Once upon a time there was a need to cache address of extent buffer
> > pages, as it was a costly operation (map_private_extent_buffer(),
> > cfed81a04eb555 ("Btrfs: add the ability to cache a pointer into the
> > eb")).  This was not even due to use of HIGHMEM, this had been removed
> > before that due to possible locking issues ( a65917156e3459 ("Btrfs:
> > stop using highmem for extent_buffers")).
> > 
> > Over the time the amount of work in the set/get helpers got reduced and
> > became quite straightforward bounds checking with an unaligned
> > read/write, commit db3756c879773c ("btrfs: remove unused
> > map_private_extent_buffer").
> 
> Thanks a lot for the history of the token accessors.
> 
> And this is also a great chance to us to sync the removal of token eb 
> accessors to the progs.
> 
> If you haven't yet started that progs removal, I'm totally fine to do that.

I usually do the kernel->progs sync before a release, inspired by the
kernel git log where it applies. I haven't started with the accessors
updates as I have a few more changes to those files pending but I
wouldn't mind if you do it now.

  reply	other threads:[~2025-06-30 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 14:03 [PATCH 0/4] Set/get accessor cleanups David Sterba
2025-06-27 14:03 ` [PATCH 1/4] btrfs: don't use token set/get accessors for btrfs_item members David Sterba
2025-06-27 14:03 ` [PATCH 2/4] btrfs: don't use token set/get accessors in inode.c:fill_inode_item() David Sterba
2025-06-27 14:03 ` [PATCH 3/4] btrfs: tree-log: don't use token set/get accessors in fill_inode_item() David Sterba
2025-06-27 14:03 ` [PATCH 4/4] btrfs: accessors: delete token versions of set/get helpers David Sterba
2025-06-29  1:13   ` Qu Wenruo
2025-06-30 16:11     ` David Sterba [this message]
2025-06-29  1:18 ` [PATCH 0/4] Set/get accessor cleanups Qu Wenruo
2025-06-30 15:54   ` David Sterba
2025-06-30  6:25 ` Johannes Thumshirn

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=20250630161159.GI31241@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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