From: Wei Yang <richard.weiyang@gmail.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, maple-tree@lists.infradead.org,
linux-mm@kvack.org, Sidhartha Kumar <sidhartha.kumar@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH v3 4/5] maple_tree: refine mas_store_root() on storing NULL
Date: Sat, 19 Oct 2024 00:59:29 +0000 [thread overview]
Message-ID: <20241019005929.ed5wuhbvdhtfqk2o@master> (raw)
In-Reply-To: <wwfvyu5gefgs2cyec7zjbyxz3vo3wle6vkojqnmztngxa7erwy@xgqhvqyc2ibu>
On Fri, Oct 18, 2024 at 02:12:08PM -0400, Liam R. Howlett wrote:
>* Liam R. Howlett <Liam.Howlett@oracle.com> [241018 14:00]:
>> * Liam R. Howlett <Liam.Howlett@oracle.com> [241018 13:57]:
>> > * Wei Yang <richard.weiyang@gmail.com> [241017 22:40]:
>> > > Currently, when storing NULL on mas_store_root(), the behavior could be
>> > > improved.
>> > >
>> > > For example possible cases are:
>> > >
>> > > * store NULL at any range result a new node
>> > > * store NULL at range [m, n] where m > 0 to a single entry tree result
>> > > a new node with range [m, n] set to NULL
>> > > * store NULL at range [m, n] where m > 0 to an empty tree result
>> > > consecutive NULL slot
>> > >
>> > > This patch tries to improve in:
>> > >
>> > > * memory efficient by setting to empty tree instead of using a node
>> >
>> > > * remove the possibility of consecutive NULL slot which will prohibit
>> > > extended null in later operation
>> >
>> > I don't understand this. Do we actually store consecutive NULLs now?
>> >
>> > This is a very odd change log for fixing an optimisation. Maybe start
>> > by explaining how we end up with a node with a single value now, then
>> > state how this code changes that?
>> >
Let me reply all at here.
We may have some cases to result in consecutive NULL slots now.
For example, we store NULL at range [3, 10] to an empty tree.
maple_tree(0x7fff2b797170) flags 5, height 1 root 0x615000000d0e
0-18446744073709551615: node 0x615000000d00 depth 0 type 1 parent 0x7fff2b797171 contents: (nil) 2 (nil) 10 (nil) 18446744073709551615 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 0x2
0-2: (nil)
3-10: (nil)
11-18446744073709551615: (nil)
Or we first store an element to [0, 0] and then store NULL at range [2, 5]
maple_tree(0x7fff2b797170) flags 5, height 1 root 0x61500000150e
0-18446744073709551615: node 0x615000001500 depth 0 type 1 parent 0x7fff2b797171 contents: 0x7fff2b797000 0 (nil) 1 (nil) 5 (nil) 18446744073709551615 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 (nil) 0 0x3
0: 0x7fff2b797000
1: (nil)
2-5: (nil)
6-18446744073709551615: (nil)
These are the cases to be checked in new test cases in patch 5.
Maybe we can put this examples in change log for clarifying?
>> > >
>> > > Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> > > CC: Liam R. Howlett <Liam.Howlett@Oracle.com>
>> > > CC: Sidhartha Kumar <sidhartha.kumar@oracle.com>
>> > > CC: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>> > >
>> > > ---
>> > > v3: move change into mas_store_root()
>> > > ---
>> > > lib/maple_tree.c | 6 +++++-
>> > > 1 file changed, 5 insertions(+), 1 deletion(-)
>> > >
>> > > diff --git a/lib/maple_tree.c b/lib/maple_tree.c
>> > > index db8b89487c98..03fbee9880eb 100644
>> > > --- a/lib/maple_tree.c
>> > > +++ b/lib/maple_tree.c
>> > > @@ -3439,7 +3439,11 @@ static inline void mas_root_expand(struct ma_state *mas, void *entry)
>> > >
>> > > static inline void mas_store_root(struct ma_state *mas, void *entry)
>> > > {
>> > > - if (likely((mas->last != 0) || (mas->index != 0)))
>> > > + if (!entry) {
>> > > + void *contents = mas_root_locked(mas);
>> > > +
>> > > + if (!mas->index && contents)
>> > > + rcu_assign_pointer(mas->tree->ma_root, NULL);
>> >
>> > You are changing what used to handle any range that wasn't 0 to handle
>> > storing NULL.
>> >
>> > This seems really broken.
>
>I understand now. You don't need to get the contents though
>
>if (!mas->index && mas_is_ptr(mas)) will work
>
>But it's probably faster to just assign the NULL and not check anything.
>
We should at least check the new range cover [0, 0]. Otherwise it will
overwrite it if it is originally a single entry tree.
This works fine:
if (!mas->index)
rcu_assign_pointer(mas->tree->ma_root, NULL);
I would change to this, if you are ok with it.
>> >
>> > > + } else if (likely((mas->last != 0) || (mas->index != 0)))
>> >
>> > Isn't this exactly what you have above in the if statement?
>>
>> Oh, I see. It's the same as the line you deleted above.
>>
>> >
>> > > mas_root_expand(mas, entry);
>> > > else if (((unsigned long) (entry) & 3) == 2)
>> > > mas_root_expand(mas, entry);
>> > > --
>> > > 2.34.1
>> > >
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2024-10-19 0:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 2:39 [PATCH v3 0/5] refine " Wei Yang
2024-10-18 2:39 ` [PATCH v3 1/5] maple_tree: print empty for an empty tree on mt_dump() Wei Yang
2024-10-18 2:39 ` [PATCH v3 2/5] maple_tree: the return value of mas_root_expand() is not used Wei Yang
2024-10-18 2:39 ` [PATCH v3 3/5] maple_tree: not necessary to check index/last again Wei Yang
2024-10-18 17:43 ` Liam R. Howlett
2024-10-19 0:28 ` Wei Yang
2024-10-18 2:39 ` [PATCH v3 4/5] maple_tree: refine mas_store_root() on storing NULL Wei Yang
2024-10-18 17:57 ` Liam R. Howlett
2024-10-18 18:00 ` Liam R. Howlett
2024-10-18 18:12 ` Liam R. Howlett
2024-10-19 0:59 ` Wei Yang [this message]
2024-10-19 1:55 ` Liam R. Howlett
2024-10-19 2:38 ` Wei Yang
2024-10-18 2:39 ` [PATCH v3 5/5] maple_tree: add a test checking storing null Wei Yang
2024-10-18 18:03 ` [PATCH v3 0/5] refine storing NULL Liam R. Howlett
2024-10-19 0:27 ` 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=20241019005929.ed5wuhbvdhtfqk2o@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=maple-tree@lists.infradead.org \
--cc=sidhartha.kumar@oracle.com \
/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