All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Viacheslav A.Dubeyko <viacheslav.dubeyko@bytedance.com>
Cc: <lsf-pc@lists.linux-foundation.org>, <linux-cxl@vger.kernel.org>,
	<linux-mm@kvack.org>, Dan Williams <dan.j.williams@intel.com>,
	"Adam Manzanares" <a.manzanares@samsung.com>
Subject: Re: [LSF/MM/BPF BoF] Session for CXL memory
Date: Tue, 24 Jan 2023 10:12:55 +0000	[thread overview]
Message-ID: <20230124101255.000016a5@Huawei.com> (raw)
In-Reply-To: <38D49DA9-3C57-4951-8CBA-5D2BB0C40D9C@bytedance.com>

On Fri, 6 Jan 2023 14:20:42 -0800
"Viacheslav A.Dubeyko" <viacheslav.dubeyko@bytedance.com> 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. 

The fabric manager is rather disconnected from the host side of things (all
out of band communications), so it would be a stretch to build a stand alone
topic around that for LSF-MM. If we have the right people in the room /
online, it would be good to discuss it (so part of a wider sessions on CXL).
I'd love to get some traction before LSFMM though! Host aspects such as
Dynamic Capacity Devices and sharing feel more LSFMM suitable.
 
> >I am going to share the topic in separate email.

Did I miss the email, or not sent yet?  That topic is obscure enough we definitely
need some background if anyone outside of CXL folk is going to have any idea what
we are talking about.

> > would like to suggest a special session for CXL memory
> > related topics.
> > 
> > How everybody feels about it?

A lot of the interesting bits currently strike me as rather speculative
(no code), so sessions might not be as productive as shooting at an
implementation. That's less true of FM stuff as we really do need
an outline of an architecture plus some planning on that.

Could we have something to shoot at for other topics in the
time frame?  maybe...

I'm definitely interested in general in CXL enablement topics
and FM side of things.

Jonathan


> > 
> > Thanks,
> > Slava.
> >   
> 



  parent reply	other threads:[~2023-01-24 10:13 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       ` [Lsf-pc] " Dan Williams
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 [this message]
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=20230124101255.000016a5@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --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.