From: Peng Zhang <zhangpeng.00@bytedance.com>
To: Liam.Howlett@oracle.com
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, maple-tree@lists.infradead.org,
Peng Zhang <zhangpeng.00@bytedance.com>
Subject: [PATCH v2 00/10] Clean ups for maple tree
Date: Wed, 17 May 2023 16:57:59 +0800 [thread overview]
Message-ID: <20230517085809.86522-1-zhangpeng.00@bytedance.com> (raw)
Some clean ups, mainly to make the code of maple tree more concise.
This patchset has passed the self-test.
0006-0009 - Make mas_wr_modify() and its subfunctions clearer. Make the
store operation of maple tree more efficient in some cases.
Thanks Liam and Matthew.
Changes since v1:
- Rework mtree_alloc_{range,rrange}() instead of removing it. [01/10]
- Fix the arguments to __must_hold() instead of removing it. [03/10]
- Keep the fast path. Expand the compact code. [04/10]
- Drop "maple_tree: Wrap the replace operation with an inline
function.". [v1 06/10]
- Remove some comments. [07/10] [08/10]
- Avoid modifying wr_mas->offset_end in mas_wr_modify(). [09/10]
- Add a patch to relocate mas_empty_area_rev(). [10/10]
Peng Zhang (10):
maple_tree: Rework mtree_alloc_{range,rrange}()
maple_tree: Drop mas_{rev_}alloc() and mas_fill_gap()
maple_tree: Fix the arguments to __must_hold()
maple_tree: Simplify mas_is_span_wr()
maple_tree: Make the code symmetrical in mas_wr_extend_null()
maple_tree: Add mas_wr_new_end() to calculate new_end accurately
maple_tree: Add comments and some minor cleanups to mas_wr_append()
maple_tree: Rework mas_wr_slot_store() to be cleaner and more
efficient.
maple_tree: Simplify and clean up mas_wr_node_store()
maple_tree: Relocate the declaration of mas_empty_area_rev().
include/linux/maple_tree.h | 12 +-
lib/maple_tree.c | 455 +++++++++++++------------------------
2 files changed, 160 insertions(+), 307 deletions(-)
--
2.20.1
next reply other threads:[~2023-05-17 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 8:57 Peng Zhang [this message]
2023-05-17 8:58 ` [PATCH v2 01/10] maple_tree: Rework mtree_alloc_{range,rrange}() Peng Zhang
2023-05-17 18:17 ` Liam R. Howlett
2023-05-18 6:10 ` Peng Zhang
2023-05-18 13:47 ` Liam R. Howlett
2023-05-17 8:58 ` [PATCH v2 02/10] maple_tree: Drop mas_{rev_}alloc() and mas_fill_gap() Peng Zhang
2023-05-17 8:58 ` [PATCH v2 03/10] maple_tree: Fix the arguments to __must_hold() Peng Zhang
2023-05-17 8:58 ` [PATCH v2 04/10] maple_tree: Simplify mas_is_span_wr() Peng Zhang
2023-05-17 18:35 ` Liam R. Howlett
2023-05-17 8:58 ` [PATCH v2 05/10] maple_tree: Make the code symmetrical in mas_wr_extend_null() Peng Zhang
2023-05-17 8:58 ` [PATCH v2 06/10] maple_tree: Add mas_wr_new_end() to calculate new_end accurately Peng Zhang
2023-05-17 19:21 ` Liam R. Howlett
2023-05-17 8:58 ` [PATCH v2 07/10] maple_tree: Add comments and some minor cleanups to mas_wr_append() Peng Zhang
2023-05-17 19:33 ` Liam R. Howlett
2023-05-18 9:27 ` Peng Zhang
2023-05-17 8:58 ` [PATCH v2 08/10] maple_tree: Rework mas_wr_slot_store() to be cleaner and more efficient Peng Zhang
2023-05-17 22:48 ` Liam R. Howlett
2023-05-18 9:27 ` Peng Zhang
2023-05-17 8:58 ` [PATCH v2 09/10] maple_tree: Simplify and clean up mas_wr_node_store() Peng Zhang
2023-05-17 8:58 ` [PATCH v2 10/10] maple_tree: Relocate the declaration of mas_empty_area_rev() Peng Zhang
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=20230517085809.86522-1-zhangpeng.00@bytedance.com \
--to=zhangpeng.00@bytedance.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.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