From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Maple Tree Proposed Features
Date: Thu, 2 May 2024 15:48:33 -0400 [thread overview]
Message-ID: <t2gvqeel4gbjyfk2g2mezuwwarlfgdbxw7xn4y366lv26pb6g6@m4rhm4u3w2ed> (raw)
In-Reply-To: <20240502105304.m44vwdqtirhxhgro@quack3>
* Jan Kara <jack@suse.cz> [240502 06:53]:
> On Tue 30-04-24 23:16:55, Liam R. Howlett via Lsf-pc wrote:
> > 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.
>
> I'd be interested in this. Not sure how much discussion to expect from this
> though. Do you expect this will take a full slot or would perhaps a
> lightning talk where you share where things are going be enough? I expect
> the MM track will be rather packed as far as I've heard so I'm inquiring so
> that we can pick the most sensible scheduling...
I'm not sure a full slot is necessary either. If there's room for a
half-slot, that might be enough.
This is too technical for other conferences, but also not quite the same
type of discussion that is typical at lsf either.
Thanks,
Liam
prev parent reply other threads:[~2024-05-02 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 3:16 [LSF/MM/BPF TOPIC] Maple Tree Proposed Features Liam R. Howlett
2024-05-02 10:53 ` [Lsf-pc] " Jan Kara
2024-05-02 19:48 ` Liam R. Howlett [this message]
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=t2gvqeel4gbjyfk2g2mezuwwarlfgdbxw7xn4y366lv26pb6g6@m4rhm4u3w2ed \
--to=liam.howlett@oracle.com \
--cc=jack@suse.cz \
--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).