Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.g.garry@oracle.com>
Cc: Alan Adamson <alan.adamson@oracle.com>,
	linux-nvme@lists.infradead.org, kch@nvidia.com,
	kbusch@kernel.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH v3 2/2] nvme: all namespaces in a subsystem must adhere to a common atomic write size
Date: Wed, 14 May 2025 07:35:46 +0200	[thread overview]
Message-ID: <20250514053546.GA24782@lst.de> (raw)
In-Reply-To: <9ae170fd-0f27-4da7-b475-61530b061c85@oracle.com>

On Tue, May 13, 2025 at 10:45:33AM +0100, John Garry wrote:
>> +		 * Set subsystem atomic bs.
>> +		 */
>> +		if (ns->ctrl->subsys->atomic_bs) {
>> +			if (atomic_bs > ns->ctrl->subsys->atomic_bs) {
>
> I am not sure why use > and not !=
>
>> +				pr_err_ratelimited(
>
> could dev_err() be used?

Yes and yes.

>
> "%s: Inconsistent Atomic Write Size,
>
> we could mention that this is the powerfail atomic size, and not "normal". 
> But I suppose that we don't use "normal" values anywhere, so it could be 
> assumed.

I'll keep it as-is, the message is already borderling too long as is.

>> --- a/drivers/nvme/host/nvme.h
>> +++ b/drivers/nvme/host/nvme.h
>> @@ -410,6 +410,7 @@ struct nvme_ctrl {
>>     	enum nvme_ctrl_type cntrltype;
>>   	enum nvme_dctype dctype;
>> +	u16 awupf;
>
> was it intentional to lose the " 0's based awupf value" comment?

I'll add it back.

Can I get a formal review tag after this?


  reply	other threads:[~2025-05-14  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 22:37 [PATCH v3 0/2] NVMe Atomic Write fixes Alan Adamson
2025-05-08 22:38 ` [PATCH v3 1/2] nvme: multipath: enable BLK_FEAT_ATOMIC_WRITES for multipathing Alan Adamson
2025-05-15  2:51   ` Chaitanya Kulkarni
2025-05-08 22:38 ` [PATCH v3 2/2] nvme: all namespaces in a subsystem must adhere to a common atomic write size Alan Adamson
2025-05-13  9:45   ` John Garry
2025-05-14  5:35     ` Christoph Hellwig [this message]
2025-05-14  7:03       ` John Garry
2025-05-14 13:57         ` Christoph Hellwig
2025-05-15  2:54   ` Chaitanya Kulkarni
2025-05-13  6:17 ` [PATCH v3 0/2] NVMe Atomic Write fixes 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=20250514053546.GA24782@lst.de \
    --to=hch@lst.de \
    --cc=alan.adamson@oracle.com \
    --cc=john.g.garry@oracle.com \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.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