From: Chaitanya Kulkarni <kch@nvidia.com>
To: <linux-nvme@lists.infradead.org>
Cc: <kbusch@kernel.org>, <hch@lst.de>, <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [RFC PATCH 0/2] nvme: nvme_setup_cmd() cleanup
Date: Wed, 9 Mar 2022 09:04:35 -0800 [thread overview]
Message-ID: <20220309170437.4448-1-kch@nvidia.com> (raw)
Hi,
This cleans up the nvme_setup_cmd() so that it reduces number calls
to nvme_setup_zone_mgmt_send() and nvme_setup_rw() along with removing
an extra parameter to those functions.
Full this is partially tested code.
-ck
Chaitanya Kulkarni (2):
nvme: derive zone-mgmt-act from struct request
nvme: derive nvme cmd opcode from struct request
drivers/nvme/host/core.c | 27 +++++++++++----------------
drivers/nvme/host/nvme.h | 6 ++----
drivers/nvme/host/zns.c | 13 +++++++++++--
3 files changed, 24 insertions(+), 22 deletions(-)
--
2.29.0
next reply other threads:[~2022-03-09 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:04 Chaitanya Kulkarni [this message]
2022-03-09 17:04 ` [RFC PATCH 1/2] nvme: derive zone-mgmt-act from struct request Chaitanya Kulkarni
2022-03-09 17:04 ` [RFC PATCH 2/2] nvme: derive nvme cmd opcode " Chaitanya Kulkarni
2022-03-14 7:22 ` [RFC PATCH 0/2] nvme: nvme_setup_cmd() cleanup 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=20220309170437.4448-1-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@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