From: Luis Chamberlain <mcgrof@kernel.org>
To: Adam Manzanares <a.manzanares@samsung.com>, Song Liu <song@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
Fan Ni <fan.ni@samsung.com>,
"dave.jiang@intel.com" <dave.jiang@intel.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"alison.schofield@intel.com" <alison.schofield@intel.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
"gourry.memverge@gmail.com" <gourry.memverge@gmail.com>,
"wj28.lee@gmail.com" <wj28.lee@gmail.com>,
"rientjes@google.com" <rientjes@google.com>,
"ruansy.fnst@fujitsu.com" <ruansy.fnst@fujitsu.com>,
"shradha.t@samsung.com" <shradha.t@samsung.com>,
Jim Harris <jim.harris@samsung.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] CXL Development Discussions
Date: Wed, 8 May 2024 12:30:13 -0700 [thread overview]
Message-ID: <ZjvSxTvu_SHWVCVK@bombadil.infradead.org> (raw)
In-Reply-To: <48a26545-5d41-47f4-95a6-e55395b63c66@nmtadam.samsung>
On Wed, May 08, 2024 at 06:38:36PM +0000, Adam Manzanares wrote:
> On Tue, May 07, 2024 at 11:50:54AM -0700, Luis Chamberlain wrote:
> > On Mon, May 06, 2024 at 04:47:37PM -0700, Dan Williams wrote:
> > > For testing I think it is an "all of the above plus hardware testing if
> > > possible" situation. My hope is to get to a point where CXL patchwork
> > > lights up "S/W/F" columns with backend tests similar to NETDEV
> > > patchwork:
> > >
> > > https://patchwork.kernel.org/project/netdevbpf/list/
> > >
> > > There are some initial discussions about how to do this likely we can
> > > grab some folks to discuss more.
> > >
> > > I think Paul and Song would be useful to have for this discussion.
> >
> > I think everyone and their aunt wants this to happen for their subsystem,
> > so a separate session to hear about how to get there would be nice.
>
> +1
Song, at last year's LSFMM you had mentioned the above work by ebpf folks
with patchwork integration. While it is great, I am not sure if folks
realize the amount of work required to get the above up and running and
then to maintain it. So I was wondering if perhaps at this year's LSFMM
if we can have a lightning talk or BoF to review just that and give
people clarity about the effort required to do get this going and
maintaining it. Its clear not only CXL folks would be interested, but
also filesystems and likely block layer folks. Would you be up to help
review that with folks with a lightning talk or BoF session? Would there
be anyone else who can talk about that?
Luis
next prev parent reply other threads:[~2024-05-08 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240506192712uscas1p225316f79bb69f979b647d2a06a00a25f@uscas1p2.samsung.com>
2024-05-06 19:27 ` [LSF/MM/BPF TOPIC] CXL Development Discussions Adam Manzanares
2024-05-06 20:28 ` Dave Jiang
2024-05-06 22:58 ` Dan Williams
2024-05-08 18:08 ` Adam Manzanares
2024-05-06 23:47 ` Dan Williams
2024-05-07 18:50 ` Luis Chamberlain
2024-05-08 18:38 ` Adam Manzanares
2024-05-08 19:30 ` Luis Chamberlain [this message]
2024-05-09 18:14 ` Song Liu
2024-05-09 4:19 ` Dan Williams
2024-05-08 18:26 ` Adam Manzanares
2024-05-07 11:48 ` Michal Hocko
2024-05-08 18:35 ` Adam Manzanares
2024-05-12 13:07 ` Michal Hocko
2024-05-13 12:12 ` Davidlohr Bueso
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=ZjvSxTvu_SHWVCVK@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=gourry.memverge@gmail.com \
--cc=ira.weiny@intel.com \
--cc=jim.harris@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=ruansy.fnst@fujitsu.com \
--cc=shradha.t@samsung.com \
--cc=song@kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=wj28.lee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).