From: Davidlohr Bueso <dave@stgolabs.net>
To: linux-cxl@vger.kernel.org, linux-mm@kvack.org,
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
Subject: Re: [ANNOUNCE/CFP] CXL Microconference at LPC 2023
Date: Fri, 28 Jul 2023 10:57:18 -0700 [thread overview]
Message-ID: <m7qmjtzl5ttg7tt2dn63i3yit6qeg6ap7sk4isuf7hibr4chpd@2lgv47hvwqia> (raw)
In-Reply-To: <a4c2gx2tnm4ckax7qkx2trnvmqjssfytc45sb2zikuayd2marc@rpsjp4icgsvn>
On Wed, 14 Jun 2023, Davidlohr Bueso wrote:
>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/
A reminder that submissions are due on or before:
11:59PM UTC on Sunday, August 6, 2023.
Thanks,
Davidlohr
next prev parent reply other threads:[~2023-07-28 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 0:17 [ANNOUNCE/CFP] CXL Microconference at LPC 2023 Davidlohr Bueso
2023-07-28 17:57 ` Davidlohr Bueso [this message]
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=m7qmjtzl5ttg7tt2dn63i3yit6qeg6ap7sk4isuf7hibr4chpd@2lgv47hvwqia \
--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.