Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Shesha Bhushan Sreenivasamurthy <sheshas@marvell.com>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: Region ID in Initiate Dynamic Capacity Release
Date: Fri, 14 Jul 2023 12:37:10 +0100	[thread overview]
Message-ID: <20230714123710.00004140@Huawei.com> (raw)
In-Reply-To: <DM6PR18MB28445F66E323501519D4861BAF37A@DM6PR18MB2844.namprd18.prod.outlook.com>

On Thu, 13 Jul 2023 21:54:47 +0000
Shesha Bhushan Sreenivasamurthy <sheshas@marvell.com> wrote:

> Hello All,
>    In "Initiate Dynamic Capacity Add Request", LD-ID and region-id to which capacity is added are specified. However, in case of "Initiate Dynamic Capacity Release", no region-id is specified in the request payload. However, specification says that f "Initiate Dynamic Capacity Release" command fails with "Invalid Input" if invalid region-id is specified. Is this an errata ? This is true in both CXL3.0 and CXL3.1 (draft).

Hi Shesha

Please do not discuss consortium draft documents on public lists.  Here we can
only talk about those that are published.

Also, these questions are probably better addressed within the CXL consortium (SSWG) anyway.

Jonathan

> 
> Secondly, can we add capacities to 'a' LD from multiple regions, meaning, can "Initiate Dynamic Capacity Add Request", be executed twice on the same LD, with different region-ids in the two calls.
> 
> Thanks,
> Shesha.

  reply	other threads:[~2023-07-14 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 21:54 Region ID in Initiate Dynamic Capacity Release Shesha Bhushan Sreenivasamurthy
2023-07-14 11:37 ` Jonathan Cameron [this message]
2023-07-14 16:30   ` [EXT] " Shesha Bhushan Sreenivasamurthy

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=20230714123710.00004140@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=sheshas@marvell.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