All of lore.kernel.org
 help / color / mirror / Atom feed
From: MTK <kim1158@gmail.com>
To: "Viacheslav A.Dubeyko" <viacheslav.dubeyko@bytedance.com>,
	 Adam Manzanares <a.manzanares@samsung.com>
Cc: David Rientjes <rientjes@google.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>,
	 Duen-wen Hsiao <duenwen@google.com>,
	hannes@cmpxchg.org, Fan Ni <fan.ni@samsung.com>,
	 ks0204.kim@samsung.com
Subject: Re: [External] [LSF/MM/BPF BoF] Session for CXL memory
Date: Sun, 29 Jan 2023 10:59:33 +0900	[thread overview]
Message-ID: <CAARenATEHMaDKFsdLg5FqbeW1ZAtzZUsY3Dj72Po623kWQ+_VQ@mail.gmail.com> (raw)
In-Reply-To: <CAARenASO6hTw+JX-JOau6mzhvkWr20Yw0GQnYjGhE2hi239woQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2933 bytes --]

I'm sorry, forwarding as plaintext.

On Sun, Jan 29, 2023 at 10:45 AM MTK <kim1158@gmail.com> wrote:
>
> Thank you Mr. Slava and Adam for introducing our research.
>
> If I was given an opportunity, I would like to share and discuss
> - A case of memory tiering solution for CXL memory, Samsung SMDK, which
works across userspace and kernelspace : why and how
> - Some lessens learned from Industry while CXL integration
> - Proposal for possible Linux MM expansions for CXL memory
>
> Regarding FM topic, I'm also interested in what we should supports for
CXL 3.0 and later topology.
>
> All the best
> Kyungsan
>
> 2023년 1월 27일 (금) 오전 4:05, Viacheslav A.Dubeyko <
viacheslav.dubeyko@bytedance.com>님이 작성:
>>
>>
>>
>> > On Jan 26, 2023, at 8:58 AM, Adam Manzanares <a.manzanares@samsung.com>
wrote:
>> >
>> > On Mon, Jan 23, 2023 at 10:30:34AM -0800, Viacheslav A.Dubeyko wrote:
>> >>
>> >>
>> >>> On Jan 23, 2023, at 9:46 AM, Adam Manzanares <
a.manzanares@samsung.com> wrote:
>> >>>
>> >>> On Sun, Jan 22, 2023 at 09:51:19PM -0800, David Rientjes 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.
>> >>>>
>> >>>
>> >>> +1 for a normal topic proposal.
>> >>
>> >> By the way, Samsung SMDK (memory development kit) suggested memory
model
>> >> in user-space and kernel memory subsystem modification. I assume that
we need
>> >> to discuss the memory model and kernel-space modification. So, it
could be one of
>> >> the CXL related topic. Could we expect that Samsung guys deliver a
talk?
>> >
>> > +Kyungsan Kim
>> >
>> > It is my understanding that Kyungsan, who is the lead for the SMDK
project is
>> > interested in sharing with the community some lessons learned from
working with
>> > CXL attached memory and a CFP is planned.
>> >
>>
>> Sounds pretty great for me. :)
>>
>> Thanks,
>> Slava.
>>


-- 
------------------------------------------------------------
the person who practices a truth goes toward light.

[-- Attachment #2: Type: text/html, Size: 4178 bytes --]

  reply	other threads:[~2023-01-29  1:59 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 [this message]
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
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=CAARenATEHMaDKFsdLg5FqbeW1ZAtzZUsY3Dj72Po623kWQ+_VQ@mail.gmail.com \
    --to=kim1158@gmail.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=duenwen@google.com \
    --cc=fan.ni@samsung.com \
    --cc=hannes@cmpxchg.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=ks0204.kim@samsung.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.