mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Baolin Wang" <baolin.wang@linux.alibaba.com>
To: "Christoph Hellwig" <hch@lst.de>
Cc: "kbusch" <kbusch@kernel.org>, "axboe" <axboe@fb.com>,
	"sagi" <sagi@grimberg.me>,
	"baolin.wang7" <baolin.wang7@gmail.com>,
	"linux-nvme" <linux-nvme@lists.infradead.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] nvme-pci: Add controller memory buffer supported macro
Date: Wed, 24 Jun 2020 14:22:24 +0800	[thread overview]
Message-ID: <0cc93c56-57ba-42d7-8af9-348076e9d3ea.baolin.wang@linux.alibaba.com> (raw)
In-Reply-To: <20200624020716.GB40094@VM20190228-100.tbsite.net>

> On Tue, Jun 23, 2020 at 06:27:51PM +0200, Christoph Hellwig wrote:
> > On Tue, Jun 23, 2020 at 09:24:33PM +0800, Baolin Wang wrote:
> > > Introduce a new capability macro to indicate if the controller
> > > supports the memory buffer or not, instead of reading the
> > > NVME_REG_CMBSZ register.
> > 
> > This is a complex issue.  The CMBS bit was only added in NVMe 1.4 as
> > a backwards incompatible change, as the CMB addressing scheme can lead
> 
> Ah, right, I think I should add another version condition:
> if ((ctrl->vs >= NVME_VS(1, 4, 0) && !NVME_CAP_CMBS(dev->ctrl.cap)) ||
>     dev->cmb_size)
>    return;

After more thinking, now we should read NVME_REG_VS register to get the controller version
when using the CMBS bit in Capabilities register, there is no benefit, so I'll drop this patch. Thanks.

> > to data corruption.  The CMBS was added as part of the horribe hack
> > that also involves the CBA field, which we'll need to see before
> > using it to work around the addressing issue.  At the same time we
> > should also continue supporting the legacy pre-1.4 CMB with a warning
> > (and may reject it if we know we run in a VM).

  reply	other threads:[~2020-06-24  6:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 13:24 [PATCH 0/3] Some improvements for NVMe Baolin Wang
2020-06-23 13:24 ` [PATCH 1/3] nvme: Add Arbitration Burst support Baolin Wang
2020-06-23 14:40   ` Keith Busch
2020-06-23 17:39     ` Sagi Grimberg
2020-06-23 18:01       ` Keith Busch
2020-06-24  1:34         ` Baolin Wang
2020-06-24  2:51           ` Keith Busch
2020-06-24  2:54             ` Baolin Wang
2020-06-24  2:57   ` Keith Busch
2020-06-24  3:06     ` Baolin Wang
2020-06-23 13:24 ` [PATCH 2/3] nvme-pci: Add controller memory buffer supported macro Baolin Wang
2020-06-23 16:27   ` Christoph Hellwig
2020-06-24  2:07     ` Baolin Wang
2020-06-24  6:22       ` Baolin Wang [this message]
2020-06-24  2:58     ` Keith Busch
2020-06-24  5:47       ` Christoph Hellwig
2020-06-23 13:24 ` [PATCH 3/3] nvme: Use USEC_PER_SEC instead of magic numbers Baolin Wang
2020-06-23 17:39   ` Sagi Grimberg

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=0cc93c56-57ba-42d7-8af9-348076e9d3ea.baolin.wang@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=axboe@fb.com \
    --cc=baolin.wang7@gmail.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®