From: Dan Williams <dan.j.williams@intel.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>,
Dan J Williams <dan.j.williams@intel.com>,
Adam Manzanares <a.manzanares@samsung.com>, <vhache@rambus.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>, <mhocko@suse.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: RE: [RFC] Do we need dedicated LSF/MM/BPF 2024 session for CXL memory?
Date: Tue, 16 Jan 2024 11:21:20 -0800 [thread overview]
Message-ID: <65a6d730e467e_3b8e2949@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <42978BEA-D194-41F4-A619-BAF02CE8F4FF@dubeyko.com>
Viacheslav Dubeyko wrote:
> Hello,
>
> Do we need dedicated LSF/MM/BPF 2024 session for CXL memory?
Last year we handled this on the fly in terms of identifying topics that
have the highest level of cross appeal with core-mm folks. My
observation is that some of the sessions were useful for the "mm" track,
like tiering policy and ABI, while other topics were likely more
suitable for the "storage" track, like fabric manager topics.
I expect to do the same this year and not have a dedicated CXL session.
I.e. prefer CXL topics that intersect mm-policy or ABI for the "mm"
track and find a space for the more hardware-centric topics on an as
needed basis.
prev parent reply other threads:[~2024-01-16 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231222151028uscas1p1fa4d0282844f4aaa36b1133c5df17c9c@uscas1p1.samsung.com>
2023-12-22 15:10 ` [RFC] Do we need dedicated LSF/MM/BPF 2024 session for CXL memory? Viacheslav Dubeyko
2024-01-03 16:53 ` Adam Manzanares
2024-01-15 8:58 ` Viacheslav Dubeyko
2024-01-31 18:25 ` Adam Manzanares
2024-01-08 12:41 ` Jonathan Cameron
2024-01-16 19:21 ` Dan Williams [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=65a6d730e467e_3b8e2949@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=slava@dubeyko.com \
--cc=vhache@rambus.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