From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Svetly Todorov <svetly.todorov@memverge.com>
Cc: <qemu-devel@nongnu.org>,
Gregory Price <gregory.price@memverge.com>,
<linux-cxl@vger.kernel.org>, <nifan.cxl@gmail.com>
Subject: Re: [PATCH RFC v2 0/3] cxl: Multi-headed Single Logical Device (MHSLD)
Date: Fri, 21 Jun 2024 18:28:33 +0100 [thread overview]
Message-ID: <20240621182833.000029c9@huawei.com> (raw)
In-Reply-To: <20240424-cxl-2024-04-22-pullahead-v2-0-a87fc4597795@memverge.com>
On Wed, 24 Apr 2024 13:04:05 -0700
Svetly Todorov <svetly.todorov@memverge.com> wrote:
> MHSLDs allow multiple hosts to access dynamic capacity on a single
> backing device. This complicates DC management because adds,
> removals, and accesses need to be vetted such that hosts don't
> stomp on each other's data.
>
> This patchset proposes a set of hooks to be called in cxl_type3.c
> when each of the above events happens. The results of the hooks
> can be used to prevent illegal DC operations in the corresponding
> cxl_* functions.
Hi,
I had a quick go at applying this to my gitlab tree cxl staging tree
to make it more generally available. It unfortunately needs some updates
for the change to Extent Groups in the most recent DCD code.
Whilst I can probably sort that, it's going to happen particularly soon.
I'll be pushing a new tree shortly if you have time to rebase.
Jonathan
prev parent reply other threads:[~2024-06-21 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 20:04 [PATCH RFC v2 0/3] cxl: Multi-headed Single Logical Device (MHSLD) Svetly Todorov
2024-04-24 20:04 ` [PATCH RFC v2 1/3] cxl-mailbox-utils: move CXLUpdateDCExtentListInPl into header Svetly Todorov
2024-04-24 20:04 ` [PATCH RFC v2 2/3] cxl_type3: add MHD callbacks Svetly Todorov
2024-04-24 20:04 ` [PATCH RFC v2 3/3] mhsld: implement MHSLD device Svetly Todorov
2024-06-21 17:28 ` Jonathan Cameron [this message]
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=20240621182833.000029c9@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=gregory.price@memverge.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nifan.cxl@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=svetly.todorov@memverge.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