qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
	"Damien Le Moal" <Damien.LeMoal@wdc.com>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
	"Niklas Cassel" <Niklas.Cassel@wdc.com>,
	"Klaus Jensen" <k.jensen@samsung.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Max Reitz" <mreitz@redhat.com>,
	"Alistair Francis" <Alistair.Francis@wdc.com>,
	"Keith Busch" <kbusch@kernel.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Matias Bjorling" <Matias.Bjorling@wdc.com>
Subject: Re: [PATCH v11 00/13] hw/block/nvme: Support Namespace Types and Zoned Namespace Command Set
Date: Fri, 11 Dec 2020 07:37:37 +0100	[thread overview]
Message-ID: <X9MTsbXZQv4l0QYj@apples.localdomain> (raw)
In-Reply-To: <BN8PR04MB5940316D7867218AC28E0519E1CB0@BN8PR04MB5940.namprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2839 bytes --]

On Dec 10 19:25, Dmitry Fomichev wrote:
> > -----Original Message-----
> > From: Klaus Jensen <its@irrelevant.dk>
> > Sent: Wednesday, December 9, 2020 4:58 AM
> > To: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
> > Cc: Keith Busch <kbusch@kernel.org>; Klaus Jensen
> > <k.jensen@samsung.com>; Kevin Wolf <kwolf@redhat.com>; Philippe
> > Mathieu-Daudé <philmd@redhat.com>; Max Reitz <mreitz@redhat.com>;
> > Maxim Levitsky <mlevitsk@redhat.com>; Fam Zheng <fam@euphon.net>;
> > Niklas Cassel <Niklas.Cassel@wdc.com>; Damien Le Moal
> > <Damien.LeMoal@wdc.com>; qemu-block@nongnu.org; qemu-
> > devel@nongnu.org; Alistair Francis <Alistair.Francis@wdc.com>; Matias
> > Bjorling <Matias.Bjorling@wdc.com>
> > Subject: Re: [PATCH v11 00/13] hw/block/nvme: Support Namespace Types
> > and Zoned Namespace Command Set
> > 
> > Hi Dmitry,
> > 
> > By and large, this looks OK to me. There are still some issues here and
> > there, and some comments of mine that you did not address, but I will
> > follow up with patches to fix that. Let's get this merged.
> > 
> > It looks like the nvme-next you rebased on is slightly old and missing
> > two commits:
> > 
> >   "hw/block/nvme: remove superfluous NvmeCtrl parameter" and
> >   "hw/block/nvme: pull aio error handling"
> > 
> > It caused a couple of conflicts, but nothing that I couldn't fix up.
> > 
> > Since I didn't manage to convince anyone about the zsze and zcap
> > parameters being in terms of LBAs, I'll revert that to be
> > 'zoned.zone_size' and 'zoned.zone_capacity'.
> > 
> > Finally, would you accept that we skip "hw/block/nvme: Add injection of
> > Offline/Read-Only zones" for now? I'd like to discuss it a bit since I
> > think the random injects feels a bit ad-hoc. Back when I did OCSSD
> > emulation with Hans, we did something like this for setting up state
> > through a descriptor text file - I think we should explore something
> > like that before we lock down the two parameters. I'll amend the final
> > documentation commit to not include those parameters.
> > 
> > Sounds good?
> 
> Klaus,
> 
> Sounds great! Sure, we can leave out the injection patch. It  was made
> to increase our internal test coverage, but it is not ideal. Since the zones
> are injected randomly, there is no consistency between test runs and
> it is impossible to reliably create many specific test cases (e.g. the first or
> the last zone is offline).

Yes, exactly.

> The descriptor input file seems like a much more
> flexible and capable approach. If you have something in works, I'll be
> happy to discuss or review.
> 

Sure, I'll rip some stuff from OCSSD and cook up a patch.

> Thank you for your very thorough reviews!
> 

Thanks for contributing this.

Keith, you wanna take a look an give this an Ack or so?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-12-11  6:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 20:03 [PATCH v11 00/13] hw/block/nvme: Support Namespace Types and Zoned Namespace Command Set Dmitry Fomichev
2020-12-08 20:03 ` [PATCH v11 01/13] hw/block/nvme: Process controller reset and shutdown differently Dmitry Fomichev
2020-12-08 20:03 ` [PATCH v11 02/13] hw/block/nvme: Generate namespace UUIDs Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 03/13] hw/block/nvme: Separate read and write handlers Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 04/13] hw/block/nvme: Combine nvme_write_zeroes() and nvme_write() Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 05/13] hw/block/nvme: Add Commands Supported and Effects log Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 06/13] hw/block/nvme: Add support for Namespace Types Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 07/13] hw/block/nvme: Support allocated CNS command variants Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 08/13] block/nvme: Make ZNS-related definitions Dmitry Fomichev
2020-12-09  6:37   ` Klaus Jensen
2020-12-15 16:28     ` Stefan Hajnoczi
2020-12-08 20:04 ` [PATCH v11 09/13] hw/block/nvme: Support Zoned Namespace Command Set Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 10/13] hw/block/nvme: Introduce max active and open zone limits Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 11/13] hw/block/nvme: Support Zone Descriptor Extensions Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 12/13] hw/block/nvme: Add injection of Offline/Read-Only zones Dmitry Fomichev
2020-12-08 20:04 ` [PATCH v11 13/13] hw/block/nvme: Document zoned parameters in usage text Dmitry Fomichev
2020-12-09  9:57 ` [PATCH v11 00/13] hw/block/nvme: Support Namespace Types and Zoned Namespace Command Set Klaus Jensen
2020-12-10 19:25   ` Dmitry Fomichev
2020-12-11  6:37     ` Klaus Jensen [this message]
2021-01-08  6:51   ` Klaus Jensen
2020-12-16  0:23 ` Keith Busch

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=X9MTsbXZQv4l0QYj@apples.localdomain \
    --to=its@irrelevant.dk \
    --cc=Alistair.Francis@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=Dmitry.Fomichev@wdc.com \
    --cc=Matias.Bjorling@wdc.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=fam@euphon.net \
    --cc=k.jensen@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).