public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@meta.com>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
	Keith Busch <kbusch@kernel.org>, "hch@lst.de" <hch@lst.de>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme: implement support for nvme relaxed effects
Date: Tue, 6 Feb 2024 07:58:44 +0000	[thread overview]
Message-ID: <3c8443fd-fd61-48ef-b4a3-0e6545990140@nvidia.com> (raw)
In-Reply-To: <20240205191703.2990948-1-kbusch@meta.com>

Keith,

On 2/5/24 11:17, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> NVM Express TP4167 provides a way for controllers to report a relaxed
> execution constraint. Specifically, it notifies of exclusivity for IO
> vs. admin commands instead of grouping these together. If set, then we
> don't need to freeze IO in order to execute that admin command. The
> freezing distrupts IO processes, so it's nice to avoid that if the
> controller tells us we don't need to do that.
>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
>   drivers/nvme/host/core.c | 4 ++++
>   include/linux/nvme.h     | 1 +
>   2 files changed, 5 insertions(+)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 975245527c1fc..75927e8579857 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -1153,6 +1153,10 @@ u32 nvme_command_effects(struct nvme_ctrl *ctrl, struct nvme_ns *ns, u8 opcode)
>   		effects &= ~NVME_CMD_EFFECTS_CSE_MASK;
>   	} else {
>   		effects = le32_to_cpu(ctrl->effects->acs[opcode]);
> +
> +		/* Ignore execution restrictions if any relaxation bits are set */

not a blocker, but I found following much cleaner and easy to search in 
spec :-

+               /*
+                *  Command Submission and Execution Relaxation (CSER) takes
+                *  priority over Command Submission and Execution (CSE).
+                */

but if others are okay with original comment, looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck

> +		if (effects & NVME_CMD_EFFECTS_CSER_MASK)
> +			effects &= ~NVME_CMD_EFFECTS_CSE_MASK;
>   	}
>   
>   	return effects;
> diff --git a/include/linux/nvme.h b/include/linux/nvme.h
> index bc605ec4a3fd0..3ef4053ea9500 100644
> --- a/include/linux/nvme.h
> +++ b/include/linux/nvme.h
> @@ -646,6 +646,7 @@ enum {
>   	NVME_CMD_EFFECTS_NCC		= 1 << 2,
>   	NVME_CMD_EFFECTS_NIC		= 1 << 3,
>   	NVME_CMD_EFFECTS_CCC		= 1 << 4,
> +	NVME_CMD_EFFECTS_CSER_MASK	= GENMASK(15, 14),
>   	NVME_CMD_EFFECTS_CSE_MASK	= GENMASK(18, 16),
>   	NVME_CMD_EFFECTS_UUID_SEL	= 1 << 19,
>   	NVME_CMD_EFFECTS_SCOPE_MASK	= GENMASK(31, 20),



  reply	other threads:[~2024-02-06  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 19:17 [PATCH] nvme: implement support for nvme relaxed effects Keith Busch
2024-02-06  7:58 ` Chaitanya Kulkarni [this message]
2024-02-06  8:34   ` Chaitanya Kulkarni
2024-02-06 16:05     ` Keith Busch
2024-02-06 22:52       ` Chaitanya Kulkarni
2024-02-12  6:55 ` Christoph Hellwig

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=3c8443fd-fd61-48ef-b4a3-0e6545990140@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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