All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Viacheslav A.Dubeyko <viacheslav.dubeyko@bytedance.com>,
	David Rientjes <rientjes@google.com>
Cc: Duen-wen Hsiao <duenwen@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>, <linux-cxl@vger.kernel.org>,
	<linux-mm@kvack.org>, Adam Manzanares <a.manzanares@samsung.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Dan Williams <dan.j.williams@intel.com>,
	<lsf-pc@lists.linux-foundation.org>
Subject: Re: [Lsf-pc] [External] [LSF/MM/BPF BoF] Session for CXL memory
Date: Thu, 26 Jan 2023 12:42:26 -0800	[thread overview]
Message-ID: <63d2e5b210caf_ea2222947c@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <77970B17-6154-4948-ACBF-84DB4745C591@bytedance.com>

Viacheslav A.Dubeyko wrote:
> 
> 
> > On Jan 22, 2023, at 9:51 PM, David Rientjes <rientjes@google.com> wrote:
> > 
> > On Fri, 6 Jan 2023, Viacheslav A.Dubeyko wrote:
> > 
> >> CC: LSF/MM/BPF mailing list. Sorry, missed the list.
> >> 
> >>> On Jan 6, 2023, at 11:51 AM, Viacheslav A.Dubeyko <viacheslav.dubeyko@bytedance.com> wrote:
> >>> 
> >>> Hello,
> >>> 
> >>> I believe CXL memory is hot topic now. I believe we have multiple topics
> >>> for discussion. I personally would like to discuss CXL Fabric Manager
> >>> and vision of FM architecture implementation. I am going to share the topic
> >>> in separate email. I would like to suggest a special session for CXL memory
> >>> related topics.
> >>> 
> >>> How everybody feels about it?
> >>> 
> > 
> > I think this makes a lot of sense, thanks for suggesting it.
> > 
> > Should this be a BoF or just a normal topic proposal?  I assume that there 
> > could be several different topics of interest all related to CXL.mem.
> > 
> 
> My point is to have a dedicated CXL session where we can discuss
> CXL related topics. And we can have likewise session if several CXL
> related topics will be suggested. :)

It worked well last time to have individual CXL topic proposals that
could later be grouped into multiple sessions by the planning committee.

So yes, as you mention above do send separate mails with the finer
grained CXL topic in the "Subject:" so it does not get lost in the
shuffle.

> > Specifically interesting would be the division of work between the kernel 
> > and userspace to manage memory placement on systems with locally attached 
> > CXL.  And, further, what APIs userspace would have at its disposal for 
> > explicit optimization of this placement that would exist beyond what is 
> > available for NUMA.
> > 
> 
> Yes, I think this could be important discussion. Because, for example, I am working
> on figuring out how functionality can be distributed among user-space, kernel-space,
> and firmware for the case of Fabric Manager. And I believe it could be a good topic
> that I have in mind.
> 
> > I assume we might also want to chat about CXL 2.0 extensions that would be 
> > useful, especially for cloud providers.
> > 
> 
> What CXL 2.0 extensions would be useful for cloud providers from your point of view?

...or even CXL 3.0 given that specification is released now.


  reply	other threads:[~2023-01-26 20:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 19:51 [LSF/MM/BPF BoF] Session for CXL memory Viacheslav A.Dubeyko
2023-01-06 22:20 ` Viacheslav A.Dubeyko
2023-01-23  5:51   ` David Rientjes
2023-01-23 15:57     ` Davidlohr Bueso
2023-01-23 16:08     ` Duen-wen Hsiao
2023-01-23 17:46     ` Adam Manzanares
2023-01-23 18:29       ` Matthew Wilcox
2023-01-23 18:32         ` [External] " Viacheslav A.Dubeyko
2023-01-23 18:38         ` Adam Manzanares
2023-01-23 19:28         ` Gregory Price
2023-01-23 18:30       ` [External] " Viacheslav A.Dubeyko
2023-01-26 16:58         ` Adam Manzanares
2023-01-26 19:04           ` Viacheslav A.Dubeyko
2023-01-29  1:45             ` MTK
2023-01-29  1:59               ` MTK
2023-01-30 18:08               ` Viacheslav A.Dubeyko
2023-01-23 18:26     ` Viacheslav A.Dubeyko
2023-01-26 20:42       ` Dan Williams [this message]
2023-01-24  0:22     ` Yang Shi
2023-01-24  0:57       ` Wei Xu
2023-01-25 15:04         ` Zhu Yanjun
2023-03-31 18:15           ` Dragan Stancevic
2023-02-20  4:55       ` Aneesh Kumar K.V
2023-01-24 10:12   ` Jonathan Cameron
2023-01-24 18:26     ` [External] " Viacheslav A.Dubeyko
2023-01-26 20:50       ` Dan Williams

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=63d2e5b210caf_ea2222947c@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=a.manzanares@samsung.com \
    --cc=duenwen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rientjes@google.com \
    --cc=viacheslav.dubeyko@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 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.