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 v4 0/4] Optimize the fast path of mas_store()
Date: Wed, 28 Jun 2023 15:36:53 +0800 [thread overview]
Message-ID: <20230628073657.75314-1-zhangpeng.00@bytedance.com> (raw)
Add fast paths for mas_wr_append() and mas_wr_slot_store() respectively.
The newly added fast path of mas_wr_append() is used in fork() and how
much it benefits fork() depends on how many VMAs are duplicated.
Thanks Liam for the review.
Changes since v3:
- Revise the commit log of [4/4]
v1: https://lore.kernel.org/lkml/20230602075353.5917-1-zhangpeng.00@bytedance.com/
v2: https://lore.kernel.org/lkml/20230609120347.63936-1-zhangpeng.00@bytedance.com/
v3: https://lore.kernel.org/lkml/20230615084301.97701-1-zhangpeng.00@bytedance.com/
Peng Zhang (4):
maple_tree: add test for mas_wr_modify() fast path
maple_tree: add test for expanding range in RCU mode
maple_tree: optimize mas_wr_append(), also improve duplicating VMAs
maple_tree: add a fast path case in mas_wr_slot_store()
lib/maple_tree.c | 69 +++++++++++++++++++----------
lib/test_maple_tree.c | 65 +++++++++++++++++++++++++++
tools/testing/radix-tree/maple.c | 75 ++++++++++++++++++++++++++++++++
3 files changed, 186 insertions(+), 23 deletions(-)
--
2.20.1
next reply other threads:[~2023-06-28 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 7:36 Peng Zhang [this message]
2023-06-28 7:36 ` [PATCH v4 1/4] maple_tree: add test for mas_wr_modify() fast path Peng Zhang
2023-06-28 7:36 ` [PATCH v4 2/4] maple_tree: add test for expanding range in RCU mode Peng Zhang
2023-06-28 7:36 ` [PATCH v4 3/4] maple_tree: optimize mas_wr_append(), also improve duplicating VMAs Peng Zhang
2023-06-28 7:36 ` [PATCH v4 4/4] maple_tree: add a fast path case in mas_wr_slot_store() 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=20230628073657.75314-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