All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dragan Stancevic <dragan@stancevic.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>, Wei Xu <weixugc@google.com>,
	Yang Shi <shy828301@gmail.com>
Cc: David Rientjes <rientjes@google.com>,
	"Viacheslav A.Dubeyko" <viacheslav.dubeyko@bytedance.com>,
	lsf-pc@lists.linux-foundation.org, linux-cxl@vger.kernel.org,
	linux-mm@kvack.org, Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Adam Manzanares <a.manzanares@samsung.com>,
	Duen-wen Hsiao <duenwen@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Jerome Glisse <jglisse@google.com>
Subject: Re: [LSF/MM/BPF BoF] Session for CXL memory
Date: Fri, 31 Mar 2023 13:15:28 -0500	[thread overview]
Message-ID: <7447b9ed-f000-92f9-8044-afa65ef38ce5@stancevic.com> (raw)
In-Reply-To: <d733b3a4-757a-624f-18a4-ad27b1ef1f77@linux.dev>

On 1/25/23 09:04, Zhu Yanjun wrote:
> 在 2023/1/24 8:57, Wei Xu 写道:
>> On Mon, Jan 23, 2023 at 4:22 PM Yang Shi <shy828301@gmail.com> wrote:
>>>
>>> On Sun, 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.
>>>>
>>>> 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.
>>>
>>> Yeah, in addition, how CXL hierarchy interacts with memory tiering may
>>> be an interesting topic too.
>>>
>>>>
>>>> I assume we might also want to chat about CXL 2.0 extensions that 
>>>> would be
>>>> useful, especially for cloud providers.
>>>>
>>>> I'd be happy to join in any of the proposals for these topics, just 
>>>> let me
>>>> know!
>>>
>>> +1 for me.
>>>
>>
>> I am also interested in these discussions.
> 
> +1, I am interested in this.

+1, also interested in cloud aspects


--
Peace can only come as a natural consequence
of universal enlightenment -Dr. Nikola Tesla

  reply	other threads:[~2023-03-31 18:15 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 [this message]
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=7447b9ed-f000-92f9-8044-afa65ef38ce5@stancevic.com \
    --to=dragan@stancevic.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=duenwen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=jglisse@google.com \
    --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=shy828301@gmail.com \
    --cc=viacheslav.dubeyko@bytedance.com \
    --cc=weixugc@google.com \
    --cc=yanjun.zhu@linux.dev \
    /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.