linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Peng Zhang <zhangpeng.00@bytedance.com>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	maple-tree@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Maple Tree Work
Date: Fri, 14 Jul 2023 13:57:20 +0100	[thread overview]
Message-ID: <ZLFGMGtk2WMbGhuf@casper.infradead.org> (raw)
In-Reply-To: <0152143a-b105-a413-ddf2-47f688633d97@bytedance.com>

On Thu, Jul 13, 2023 at 05:58:13PM +0800, Peng Zhang wrote:
> I have a question I want to discuss here. I noticed that the interface
> of maple tree has three different prefixes, namely mtree_*, mt_*, mas_*.
> I am curious why the interfaces prefixed with mtree_* and mt_* cannot be
> unified? I think they can be changed to mtree_* to avoid two different
> prefixes.

I haven't worried about this too much.  The long-term goal is to use
the maple tree data structure to replace the radix tree data structure
underlying the xarray and use the xarray API to access the maple tree.
The xarray API will need some enhancements to make this work, but churning
the maple tree API doesn't seem like a good use of effort.

  parent reply	other threads:[~2023-07-14 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 16:38 Maple Tree Work Liam R. Howlett
2023-07-12 11:49 ` Peng Zhang
2023-07-12 15:27   ` Liam R. Howlett
2023-07-13  8:05     ` Peng Zhang
2023-07-13 15:36       ` Liam R. Howlett
2023-07-14 12:32         ` Peng Zhang
2023-07-13  9:58 ` Peng Zhang
2023-07-13 15:52   ` Liam R. Howlett
2023-07-14 12:57   ` Matthew Wilcox [this message]
2023-07-14 13:32     ` 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=ZLFGMGtk2WMbGhuf@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=zhangpeng.00@bytedance.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;
as well as URLs for NNTP newsgroup(s).