From: Peng Zhang <zhangpeng.00@bytedance.com>
To: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
Cc: Peng Zhang <zhangpeng.00@bytedance.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, maple-tree@lists.infradead.org
Subject: Re: [PATCH v2 01/10] maple_tree: Rework mtree_alloc_{range,rrange}()
Date: Thu, 18 May 2023 14:10:09 +0800 [thread overview]
Message-ID: <d3e03ee2-284e-1e32-6273-cf21b4afcf99@bytedance.com> (raw)
In-Reply-To: <20230517181705.rdfffvfhqzlsjjlm@revolver>
在 2023/5/18 02:17, Liam R. Howlett 写道:
> * Peng Zhang <zhangpeng.00@bytedance.com> [230517 04:58]:
>> Use mas_empty_area{_rev}() to refactor mtree_alloc_{range,rrange}()
>>
>> Signed-off-by: Peng Zhang <zhangpeng.00@bytedance.com>
>> ---
>> lib/maple_tree.c | 63 ++++++++++++++++++++++++------------------------
>> 1 file changed, 32 insertions(+), 31 deletions(-)
>>
>> diff --git a/lib/maple_tree.c b/lib/maple_tree.c
>> index 4eb220008f72..e1820e90f167 100644
>> --- a/lib/maple_tree.c
>> +++ b/lib/maple_tree.c
>> @@ -6493,32 +6493,31 @@ int mtree_alloc_range(struct maple_tree *mt, unsigned long *startp,
>> {
>> int ret = 0;
>>
>> - MA_STATE(mas, mt, min, min);
>> + MA_STATE(mas, mt, 0, 0);
>> if (!mt_is_alloc(mt))
>> return -EINVAL;
>>
>> if (WARN_ON_ONCE(mt_is_reserved(entry)))
>> return -EINVAL;
>>
>> - if (min > max)
>> - return -EINVAL;
>> -
>> - if (max < size)
>> - return -EINVAL;
>> -
>> - if (!size)
>> - return -EINVAL;
>> -
>> mtree_lock(mt);
>> retry:
>> - mas.offset = 0;
>> - mas.index = min;
>> - mas.last = max - size + 1;
>> - ret = mas_alloc(&mas, entry, size, startp);
>> - if (mas_nomem(&mas, gfp))
>> - goto retry;
>> -
>> + ret = mas_empty_area(&mas, min, max, size);
>> + if (!ret) {
>> + mas_insert(&mas, entry);
>> + /*
>> + * mas_nomem() may release the lock, causing the allocated area
>> + * to be unavailable, so try to allocate a free area again.
>> + */
>> + if (mas_nomem(&mas, gfp))
>> + goto retry;
>> + }
>> mtree_unlock(mt);
>> + if (!ret) {
>
> Checking for a mas_is_err() should probably be outside if (!ret)
> statement. If mas_insert() returns something besides ENOMEM, we will
> not detect the error. I'm not sure if this is possible today since this
> should never return an -EEXISTS, but having it this way doesn't add much
> to the overhead.
I don't think there will be error that can't be detected here.
In fact, there are two sources of errors:
1. mas_empty_area(), the error number is in the variable ret,
and may also be in mas->node, but ret must contain all errors.
2. mas_insert(), the error number is in mas->node
When we check errors, we should first check errors from
mas_empty_area(). If there is no error in mas_empty_area(), we
will check errors from mas_insert().
So, mas_is_err() is inside the if (!ret) statement, no problem here.
Of course, even if mas_insert() returns -EEXISTS, it can be detected
under the current encoding, because "if (!ret)" is true in this case.
But I don't think this can happen, if it happens, it's a bug of maple
tree.
I don't think it's good to put mas_is_err() outside, because the error
number stored in mas->node may come from mas_empty_area(). We should use
the ret variable to detect the error from mas_empty_area() first.
>
>> + if (mas_is_err(&mas))
>> + return xa_err(mas.node);
>> + *startp = mas.index;
>> + }
>> return ret;
>> }
>> EXPORT_SYMBOL(mtree_alloc_range);
>> @@ -6529,29 +6528,31 @@ int mtree_alloc_rrange(struct maple_tree *mt, unsigned long *startp,
>> {
>> int ret = 0;
>>
>> - MA_STATE(mas, mt, min, max - size + 1);
>> + MA_STATE(mas, mt, 0, 0);
>> if (!mt_is_alloc(mt))
>> return -EINVAL;
>>
>> if (WARN_ON_ONCE(mt_is_reserved(entry)))
>> return -EINVAL;
>>
>> - if (min > max)
>> - return -EINVAL;
>> -
>> - if (max < size - 1)
>> - return -EINVAL;
>> -
>> - if (!size)
>> - return -EINVAL;
>> -
>> mtree_lock(mt);
>> retry:
>> - ret = mas_rev_alloc(&mas, min, max, entry, size, startp);
>> - if (mas_nomem(&mas, gfp))
>> - goto retry;
>> -
>> + ret = mas_empty_area_rev(&mas, min, max, size);
>> + if (!ret) {
>> + mas_insert(&mas, entry);
>> + /*
>> + * mas_nomem() may release the lock, causing the allocated area
>> + * to be unavailable, so try to allocate a free area again.
>> + */
>> + if (mas_nomem(&mas, gfp))
>> + goto retry;
>> + }
>> mtree_unlock(mt);
>> + if (!ret) {
>
> Same here.
>
>> + if (mas_is_err(&mas))
>> + return xa_err(mas.node);
>> + *startp = mas.index;
>> + }
>> return ret;
>> }
>> EXPORT_SYMBOL(mtree_alloc_rrange);
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2023-05-18 6:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 8:57 [PATCH v2 00/10] Clean ups for maple tree Peng Zhang
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 [this message]
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=d3e03ee2-284e-1e32-6273-cf21b4afcf99@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