From: Klaus Jensen <its@irrelevant.dk>
To: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"k.jensen@samsung.com" <k.jensen@samsung.com>,
"anaidu.gollu@samsung.com" <anaidu.gollu@samsung.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"kbusch@kernel.org" <kbusch@kernel.org>
Subject: Re: [PATCH v2] hw/block/nvme: add missing mor/mar constraint checks
Date: Mon, 8 Feb 2021 09:03:18 +0100 [thread overview]
Message-ID: <YCDwRmZAeQxAJRFM@apples.localdomain> (raw)
In-Reply-To: <8f17c20687867bf2916ee44ef22211887ef349eb.camel@wdc.com>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On Feb 8 00:13, Dmitry Fomichev wrote:
> On Tue, 2021-01-26 at 13:15 +0100, Klaus Jensen wrote:
> > From: Klaus Jensen <k.jensen@samsung.com>
> >
> > Firstly, if zoned.max_active is non-zero, zoned.max_open must be less
> > than or equal to zoned.max_active.
> >
> > Secondly, if only zones.max_active is set, we have to explicitly set
> > zones.max_open or we end up with an invalid MAR/MOR configuration. This
> > is an artifact of the parameters not being zeroes-based like in the
> > spec.
> >
> > Cc: Dmitry Fomichev <dmitry.fomichev@wdc.com>
> > Reported-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
> > Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
>
> Reviewed-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
>
Thanks, applied!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-02-08 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 12:15 [PATCH v2] hw/block/nvme: add missing mor/mar constraint checks Klaus Jensen
2021-02-08 0:13 ` Dmitry Fomichev
2021-02-08 8:03 ` Klaus Jensen [this message]
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=YCDwRmZAeQxAJRFM@apples.localdomain \
--to=its@irrelevant.dk \
--cc=Dmitry.Fomichev@wdc.com \
--cc=anaidu.gollu@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@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).