All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: linux-cxl@vger.kernel.org, linux-mm@kvack.org
Cc: dan.j.williams@intel.com, a.manzanares@samsung.com,
	Jonathan.Cameron@huawei.com, fan.ni@samsung.com,
	ira.weiny@intel.com, alison.schofield@intel.com,
	dave.jiang@intel.com, vishal.l.verma@intel.com,
	gourry.memverge@gmail.com, terry.bowman@amd.com,
	rrichter@amd.com, viacheslav.dubeyko@bytedance.com,
	sheshas@marvell.com, dave@stgolabs.net
Subject: [ANNOUNCE/CFP] CXL Microconference at LPC 2023
Date: Wed, 14 Jun 2023 17:17:15 -0700	[thread overview]
Message-ID: <a4c2gx2tnm4ckax7qkx2trnvmqjssfytc45sb2zikuayd2marc@rpsjp4icgsvn> (raw)

Hello,

I am pleased to announce that we will have a CXL MC this year at Plumbers,
and hereby invite the community in our call for participation.

https://lpc.events/event/17/abstracts/1453/

Compute Express Link is a cache coherent fabric that in recent years
has been gaining momentum in the industry. CXL 3.0 launched just before
Plumbers 2022 (where very early discussions were had), bringing new
challenges such as dynamic capacity devices and large scale fabrics,
two features that bring significant challenges to Linux. There has
also been controversy and confusion in the Linux kernel community
about the state and future of CXL, regarding its usage and integration
into, for example, the core memory management subsystem. Many concerns
have been put to rest through proper clarification and setting of
expectations.

The Compute Express Link microconference focuses on how to evolve the
Linux CXL kernel driver and userspace components for support of the
CXL 2.0 spec (and beyond). The microconference provides a space to open
the discussion, incorporate more perspectives, and grow the CXL community
with a goal that the CXL Linux plumbing serves the needs of the CXL
ecosystem while balancing the needs of the Linux project. Specifically,
this microconference welcomes submissions detailing industry and academia
use cases in order to develop usage model scenarios. Finally, it will
be a good opportunity to have existing upstream CXL developers available
in a forum to discuss current CXL support and to communicate areas that
need additional involvement.

Suggested topics:
- Ecosystem & Architectural review
- Dynamic Capacity Devices
- Fabric Management
- QEMU support
- Security (ie: IDE/SPDM)
- Managing vendor specificity
- Type 2 accelerator support (bias flip management)
- Coherence management of type2/3 memory (back-invalidation)
- P2P (UIO)
- RAS (GPF, AER)
- Hotplug (QoS throttling, policies, daxctl)
- Hot remove
- Documentation
- Memory tiering topics that can relate to cxl (out of scope of MM/performance MCs)
- Industry and academia use cases

Proposals can be submitted here, by August 6th:

https://lpc.events/event/17/abstracts/

For more information, feel free to contact the Compute Express Link MC Leads:
     Davidlohr Bueso <dave@stgolabs.net>
     Jonathan Cameron <Jonathan.Cameron@Huawei.com>
     Adam Manzanares <a.manzanares@samsung.com>
     Dan Williams <dan.j.williams@intel.com>

Thank you.

             reply	other threads:[~2023-06-15  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  0:17 Davidlohr Bueso [this message]
2023-07-28 17:57 ` [ANNOUNCE/CFP] CXL Microconference at LPC 2023 Davidlohr Bueso
2023-08-11 15:49   ` 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=a4c2gx2tnm4ckax7qkx2trnvmqjssfytc45sb2zikuayd2marc@rpsjp4icgsvn \
    --to=dave@stgolabs.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=fan.ni@samsung.com \
    --cc=gourry.memverge@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rrichter@amd.com \
    --cc=sheshas@marvell.com \
    --cc=terry.bowman@amd.com \
    --cc=viacheslav.dubeyko@bytedance.com \
    --cc=vishal.l.verma@intel.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.