From: Andrew Ballance <andrewjballance@gmail.com>
To: liam.howlett@oracle.com
Cc: a.hindborg@kernel.org, akpm@linux-foundation.org,
alex.gaynor@gmail.com, aliceryhl@google.com,
andrewjballance@gmail.com, benno.lossin@proton.me,
bjorn3_gh@protonmail.com, boqun.feng@gmail.com,
brauner@kernel.org, dakr@kernel.org, dingxiangfei2009@gmail.com,
gary@garyguo.net, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
maple-tree@lists.infradead.org, ojeda@kernel.org,
rust-for-linux@vger.kernel.org, tmgross@umich.edu,
wedsonaf@gmail.com
Subject: Re: [RFC PATCH 2/2] rust: add maple tree abstractions
Date: Mon, 7 Apr 2025 15:02:50 -0500 [thread overview]
Message-ID: <20250407200250.1671534-1-andrewjballance@gmail.com> (raw)
In-Reply-To: <cons6o6begjlf4eu3wvhplimbrjtns553nugtblki7u23a3u3p@efca7vmgmr6w>
On Mon, Apr 07, 2025 at 09:59:21AM -0400, Liam R. Howlett wrote:
> * Andrew Ballance <andrewjballance@gmail.com> [250405 02:03]:
> > maple trees are sparse array like data structure that maps
> > non-overlapping ranges to pointers.
>
> Why do you think the maple tree is a spare array like data structure?
>
I called the maple tree "sparse array like" because indexes that have
no entry map to null and there can be gaps between ranges. I did not
mean to imply that a maple tree was literally a sparse array.
Would you like me to reword this?
next prev parent reply other threads:[~2025-04-07 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 6:01 [RFC PATCH 0/2] rust: add support for maple trees Andrew Ballance
2025-04-05 6:01 ` [RFC PATCH 1/2] maple_tree: add __mtree_insert_range function Andrew Ballance
2025-04-05 15:22 ` Matthew Wilcox
2025-04-05 18:38 ` Boqun Feng
2025-04-06 9:30 ` Andrew Ballance
2025-04-05 6:01 ` [RFC PATCH 2/2] rust: add maple tree abstractions Andrew Ballance
2025-04-05 15:23 ` Miguel Ojeda
2025-04-07 13:59 ` Liam R. Howlett
2025-04-07 20:02 ` Andrew Ballance [this message]
2025-04-08 1:36 ` Liam R. Howlett
2025-04-14 18:27 ` Danilo Krummrich
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=20250407200250.1671534-1-andrewjballance@gmail.com \
--to=andrewjballance@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=dingxiangfei2009@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.