From: Klaus Jensen <its@irrelevant.dk>
To: Alan Adamson <alan.adamson@oracle.com>
Cc: qemu-devel@nongnu.org, kbusch@kernel.org, qemu-block@nongnu.org
Subject: Re: [PATCH v3 0/1] hw/nvme: add atomic write support
Date: Mon, 30 Sep 2024 12:51:01 +0200 [thread overview]
Message-ID: <ZvqClfdYdTHbhtN2@AALNPWKJENSEN.aal.scsc.local> (raw)
In-Reply-To: <20240926212458.32449-1-alan.adamson@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
On Sep 26 14:24, Alan Adamson wrote:
> Changelog:
> v3: - Use cpu_to_le16() to properly handle endianness.
> - Use 'continue' rather than'break' when walking SQs.
> - No need to lock all the SQs when walking them so remove atomic_lock
> since it is running from the main loop.
>
> v2: - Include changes suggested by Klaus
> - Check for READ/WRITE commmands when walking SQs.
> - Updated the "cover-letter" below with new fio example.
>
Hi Alan,
Applied to nvme-next!
Thanks!
Klaus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-09-30 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 21:24 [PATCH v3 0/1] hw/nvme: add atomic write support Alan Adamson
2024-09-26 21:24 ` [PATCH v3 1/1] " Alan Adamson
2024-09-30 10:51 ` 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=ZvqClfdYdTHbhtN2@AALNPWKJENSEN.aal.scsc.local \
--to=its@irrelevant.dk \
--cc=alan.adamson@oracle.com \
--cc=kbusch@kernel.org \
--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).