From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, maple-tree@lists.infradead.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] simplify split calculation
Date: Wed, 13 Nov 2024 13:39:37 -0500 [thread overview]
Message-ID: <iv76oqycww7kb26lse54vovsxewdgajuk5r6kfz3rzpqpeldvh@saaxrw64xf6l> (raw)
In-Reply-To: <20241113031616.10530-1-richard.weiyang@gmail.com>
* Wei Yang <richard.weiyang@gmail.com> [241112 22:17]:
> In version 1 [1], we found current split would result into deficient node.
>
> By discussion, current implementation would lead to jitter problem.
I don't recall it leading to a jitter, I was concerned about that but I
don't think this leads to jitter.
> Since this
> is a rare case in real world, we decide to simplify the split calculation.
>
> Patch 1: simplify split calculation
> Patch 2: add a test case to check deficient node
> Patch 3: validate deficient node except for root node
>
> [1]: https://lkml.kernel.org/r/20241020024628.22469-1-richard.weiyang@gmail.com
>
> Wei Yang (3):
> maple_tree: simplify split calculation
> maple_tree: add a test check deficient node
> maple_tree: only root node could be deficient
>
> lib/maple_tree.c | 25 +++++++------------------
> lib/test_maple_tree.c | 28 ++++++++++++++++++++++++++++
> 2 files changed, 35 insertions(+), 18 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-11-13 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 3:16 Wei Yang
2024-11-13 3:16 ` [PATCH v3 1/3] maple_tree: " Wei Yang
2024-11-13 18:38 ` Liam R. Howlett
2024-11-13 3:16 ` [PATCH v3 2/3] maple_tree: add a test check deficient node Wei Yang
2024-11-13 18:40 ` Liam R. Howlett
2024-11-13 3:16 ` [PATCH v3 3/3] maple_tree: only root node could be deficient Wei Yang
2024-11-13 18:39 ` Liam R. Howlett [this message]
2024-11-14 0:53 ` [PATCH v3 0/3] simplify split calculation Wei Yang
2024-11-30 4:31 ` Andrew Morton
2024-12-01 2:02 ` Liam R. Howlett
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=iv76oqycww7kb26lse54vovsxewdgajuk5r6kfz3rzpqpeldvh@saaxrw64xf6l \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=richard.weiyang@gmail.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