All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Price <gregory.price@memverge.com>
To: Matthew Wilcox <willy@infradead.org>,
	Adam Manzanares <a.manzanares@samsung.com>
Cc: David Rientjes <rientjes@google.com>,
	Viacheslav A.Dubeyko <viacheslav.dubeyko@bytedance.com>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Duen-wen Hsiao <duenwen@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>, Fan Ni <fan.ni@samsung.com>
Subject: RE: [LSF/MM/BPF BoF] Session for CXL memory
Date: Mon, 23 Jan 2023 19:28:19 +0000	[thread overview]
Message-ID: <BN6PR17MB31211D51B9C27488D8F164A783C89@BN6PR17MB3121.namprd17.prod.outlook.com> (raw)
In-Reply-To: <Y87SIJm4XLBAmiIY@casper.infradead.org>

Dynamic Capacity Device

-----Original Message-----
From: Matthew Wilcox <willy@infradead.org> 
Sent: Monday, January 23, 2023 1:30 PM
To: Adam Manzanares <a.manzanares@samsung.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>; Duen-wen Hsiao <duenwen@google.com>; Johannes Weiner <hannes@cmpxchg.org>; Fan Ni <fan.ni@samsung.com>
Subject: Re: [LSF/MM/BPF BoF] Session for CXL memory

On Mon, Jan 23, 2023 at 05:46:00PM +0000, Adam Manzanares wrote:
> The session about DCDs at Plumbers comes to mind here. In addition, I think this

What's a DCD?


  parent reply	other threads:[~2023-01-23 19:28 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 [this message]
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
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=BN6PR17MB31211D51B9C27488D8F164A783C89@BN6PR17MB3121.namprd17.prod.outlook.com \
    --to=gregory.price@memverge.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=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 \
    --cc=willy@infradead.org \
    /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.