From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] Maple Tree Proposed Features
Date: Tue, 30 Apr 2024 23:16:55 -0400 [thread overview]
Message-ID: <rqvsoisywsbb326ybechwwgpdrdt57sngr2zwwrbp2riyi7ml5@uppobkrmbxoz> (raw)
Since there is interest (and users) in both the filesystem and mm track,
this could be a joint session. Although, I'm pretty sure there is not
enough interest for a large session.
I'd like to discuss what functionality people want/need to help their
projects, and if the maple tree is the right solution for those
problems.
I'd also like to go over common use cases of the maple tree that are
emerging and point out common pitfalls, if there is any interest in this
level of discussion.
Thanks,
Liam
next reply other threads:[~2024-05-01 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 3:16 Liam R. Howlett [this message]
2024-05-02 10:53 ` [Lsf-pc] [LSF/MM/BPF TOPIC] Maple Tree Proposed Features Jan Kara
2024-05-02 19:48 ` 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=rqvsoisywsbb326ybechwwgpdrdt57sngr2zwwrbp2riyi7ml5@uppobkrmbxoz \
--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).