From: Hongbo Li <lihongbo22@huawei.com>
To: <kent.overstreet@linux.dev>, <bfoster@redhat.com>
Cc: <linux-bcachefs@vger.kernel.org>, <lihongbo22@huawei.com>
Subject: [PATCH RFC 0/2] bcachefs: refactoring of btree_path status
Date: Wed, 20 Mar 2024 14:29:21 +0800 [thread overview]
Message-ID: <20240320062923.305431-1-lihongbo22@huawei.com> (raw)
To enhance the code readability about btree_path structure, we did
some refactoring on the relevant code based on my understanding.
Hongbo Li (2):
bcachefs: use btree_path_state to represent btree_path status
bcachefs: optimize btree_path status representation
fs/bcachefs/btree_iter.c | 22 +++++++++++-----------
fs/bcachefs/btree_iter.h | 13 +++++++++----
fs/bcachefs/btree_key_cache.c | 12 ++++++------
fs/bcachefs/btree_locking.c | 14 +++++++-------
fs/bcachefs/btree_locking.h | 8 ++++----
fs/bcachefs/btree_trans_commit.c | 2 +-
fs/bcachefs/btree_types.h | 10 +++++-----
7 files changed, 43 insertions(+), 38 deletions(-)
--
2.34.1
next reply other threads:[~2024-03-20 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 6:29 Hongbo Li [this message]
2024-03-20 6:29 ` [PATCH RFC 1/2] bcachefs: use btree_path_state to represent btree_path status Hongbo Li
2024-03-20 17:39 ` Brian Foster
2024-03-20 19:57 ` Kent Overstreet
2024-03-20 20:10 ` Kent Overstreet
2024-03-20 6:29 ` [PATCH RFC 2/2] bcachefs: optimize btree_path status representation Hongbo Li
2024-03-20 17:41 ` Brian Foster
2024-03-20 20:50 ` Kent Overstreet
2024-03-21 1:53 ` Hongbo Li
2024-03-20 20:06 ` Kent Overstreet
2024-03-21 1:44 ` Hongbo Li
2024-03-20 19:43 ` [PATCH RFC 0/2] bcachefs: refactoring of btree_path status Kent Overstreet
2024-03-20 19:55 ` Kent Overstreet
2024-03-21 2:00 ` Hongbo Li
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=20240320062923.305431-1-lihongbo22@huawei.com \
--to=lihongbo22@huawei.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).