public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Gabriel Niebler <gniebler@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Turn fs_roots_radix in btrfs_fs_info into an XArray
Date: Thu, 28 Apr 2022 14:37:48 +0300	[thread overview]
Message-ID: <db9c1003-ef3e-86fb-7bfc-9b7042485fa6@suse.com> (raw)
In-Reply-To: <b110e69e-d371-a29e-fd89-f810a4391e7b@suse.com>



On 27.04.22 г. 17:51 ч., Gabriel Niebler wrote:
> 
> Naming things is hard. Here are some ideas I've had:
> 
> BTRFS_ROOT_IN_XARRAY is obvious, but it also includes kind of a needless 
> implementation detail.
> 
> BTRFS_ROOT_IN_(FS_)ROOTS would be technically accurate, but might be 
> confusing for the reader (e.g. if they don't know about 
> btrfs_fs_indo->fs_roots of the top off their head).
> 
> BTRFS_ROOT_IN_FS_INFO_ROOTS makes that a bit clearer (someone might 
> think it refers to fbtrfs_fs_info->roots, but when they find that 
> doesn't exist they'd quickly catch on, I think), but a bit lengthy.
> 
> BTRFS_ROOT_IN_FS_INFO_FS_ROOTS is probably the most accurate, but really 
> quite long...
> 
> Does anyone else have any ideas?


BTRFS_ROOT_ACCESSIBLE/BTRFS_ROOT_REGISTERED/BTRFS_ROOT_PUBLIC/BTRFS_ROOT_INITIALIZED

because when a root goes into the root registry (either xarray or radix) 
it's essentially published to this "registry" and can be referenced by 
other parts of the filesystem. And this registration is part of the 
root's initialization sequence.

  parent reply	other threads:[~2022-04-28 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 21:45 [PATCH] btrfs: Turn fs_roots_radix in btrfs_fs_info into an XArray Gabriel Niebler
2022-04-27 14:51 ` Gabriel Niebler
2022-04-27 19:21   ` David Sterba
2022-04-28 11:37   ` Nikolay Borisov [this message]
2022-04-27 20:07 ` David Sterba
2022-04-28 11:59 ` Nikolay Borisov
2022-05-02  8:59   ` Gabriel Niebler
2022-05-02 18:39     ` David Sterba
2022-05-03  8:01     ` 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=db9c1003-ef3e-86fb-7bfc-9b7042485fa6@suse.com \
    --to=nborisov@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