From: David Sterba <dsterba@suse.cz>
To: Gabriel Niebler <gniebler@suse.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH v2] btrfs: Turn fs_info member buffer_radix into XArray
Date: Fri, 22 Apr 2022 22:32:44 +0200 [thread overview]
Message-ID: <20220422203244.GK18596@twin.jikos.cz> (raw)
In-Reply-To: <20220421154538.413-1-gniebler@suse.com>
On Thu, Apr 21, 2022 at 05:45:38PM +0200, Gabriel Niebler wrote:
> … named 'extent_buffers'. Also adjust all usages of this object to use the
> XArray API, which greatly simplifies the code as it takes care of locking
> and is generally easier to use and understand, providing notionally
> simpler array semantics.
>
> Also perform some light refactoring.
>
> Signed-off-by: Gabriel Niebler <gniebler@suse.com>
I've added the patch to for-next, seems that it survived one night test
round, so it seems to be fine. I'll move it to misc-next next week,
Nikolay was interested in reviewing the xarray patches.
next prev parent reply other threads:[~2022-04-22 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 15:45 [PATCH v2] btrfs: Turn fs_info member buffer_radix into XArray Gabriel Niebler
2022-04-22 20:32 ` David Sterba [this message]
2022-04-29 14:14 ` Nikolay Borisov
2022-04-29 18:39 ` David Sterba
2022-05-02 7:20 ` Gabriel Niebler
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=20220422203244.GK18596@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=gniebler@suse.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