From: Wei Yang <richard.weiyang@gmail.com>
To: akpm@linux-foundation.org, Liam.Howlett@oracle.com
Cc: maple-tree@lists.infradead.org, linux-mm@kvack.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH v2 0/5] refine storing NULL
Date: Thu, 17 Oct 2024 13:46:02 +0000 [thread overview]
Message-ID: <20241017134607.30206-1-richard.weiyang@gmail.com> (raw)
The original thread[1] thoughts it is a problem in mas_new_root(). But after
discussion, this should be an improvement on storing NULL.
Patch 1/2 preparation for refine.
Patch 3 remove redundant check in mas_new_root().
Patch 4 refine mas_root_expand() to improve memory efficiency and remove
possible consecutive NULL slot.
Patch 5 adds a test for storing NULL.
[1]: https://lkml.kernel.org/r/20241015233909.23592-1-richard.weiyang@gmail.com
Wei Yang (5):
maple_tree: print empty for an empty tree on mt_dump()
maple_tree: the return value of mas_root_expand() is not used
maple_tree: not necessary to check index/last again
maple_tree: refine mas_root_expand() on storing NULL
maple_tree: add a test checking storing null
lib/maple_tree.c | 32 +++++++++++---
tools/testing/radix-tree/maple.c | 73 ++++++++++++++++++++++++++++++++
2 files changed, 99 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2024-10-17 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 13:46 Wei Yang [this message]
2024-10-17 13:46 ` [PATCH v2 1/5] maple_tree: print empty for an empty tree on mt_dump() Wei Yang
2024-10-17 13:46 ` [PATCH v2 2/5] maple_tree: the return value of mas_root_expand() is not used Wei Yang
2024-10-17 13:46 ` [PATCH v2 3/5] maple_tree: not necessary to check index/last again Wei Yang
2024-10-17 13:46 ` [PATCH v2 4/5] maple_tree: refine mas_root_expand() on storing NULL Wei Yang
2024-10-17 14:10 ` Liam R. Howlett
2024-10-17 22:21 ` Wei Yang
2024-10-17 13:46 ` [PATCH v2 5/5] maple_tree: add a test checking storing null Wei Yang
2024-10-17 14:12 ` Liam R. Howlett
2024-10-17 22:24 ` Wei Yang
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=20241017134607.30206-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.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