From: Liam Howlett <liam.howlett@oracle.com>
To: "lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [LSF/MM/BPF TOPIC] The Maple Tree
Date: Tue, 1 Jun 2021 22:30:18 +0000 [thread overview]
Message-ID: <20210601223007.pvrns2kqqzuomdlm@revolver> (raw)
Over the years, the tracking of VMAs has slowly gathered more refinement
with added complexity. Currently each MM has a linked list, a tree, and
a cache to track a list of ranges. The current patch set adding the
maple tree replaces all three of these data structures and is just as
fast or faster - even without modifying the locking. As more of the MM
code is optimized to use the tree, the locking can be extracted and the
RCU benefits will begin to show.
The maple tree is a RCU safe range based B-tree. Many of the rules of a
B-tree are kept such as each leaf being at the same height and being
self-balancing. There are also fundamental differences such as how to
handle an insert operation that may cause one entry to become three or
several entries to disappear all together.
I'd like to discuss how to use the maple tree efficiently in complicated
scenarios such as those arising in the vma_adjust() scenarios. Also on
the table is the possibility of a range-based b-tree for the file
systems as it would seem to work well for file based scenarios. If
people are interested, I can also dive into how the internals of the
tree operate.
Thank you,
Liam
next reply other threads:[~2021-06-01 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 22:30 Liam Howlett [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-01 15:06 [LSF/MM/BPF TOPIC] The Maple Tree Liam Howlett
2022-02-20 17:10 ` Chaitanya Kulkarni
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=20210601223007.pvrns2kqqzuomdlm@revolver \
--to=liam.howlett@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).