From: Kanchan Joshi <joshi.k@samsung.com>
To: hch@lst.de, kbusch@kernel.org, axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, gost.dev@samsung.com,
joshiiitr@gmail.com
Subject: [PATCH v2 0/2] uring-passthrough for admin commands
Date: Fri, 20 May 2022 10:25:58 +0530 [thread overview]
Message-ID: <20220520045600.3773-1-joshi.k@samsung.com> (raw)
In-Reply-To: CGME20220520050118epcas5p1f6a930419285ecdac65afaa22255c03f@epcas5p1.samsung.com
The series enables uring-passthrough for admin-commands.
Patch 1 is prep.
Patch 2 adds new opcode for admin uring-passthrough, and enables it on
nvme controller dev(/dev/nvmeX). It reuses the code of io-command
passthrough, with the only difference that commands are issued on admin
queue.
Changes since v1:
- drop the code that supports this op over ns char device
- apply reviewed-by tag
Kanchan Joshi (2):
nvme: helper for uring-passthrough checks
nvme: enable uring-passthrough for admin commands
drivers/nvme/host/core.c | 1 +
drivers/nvme/host/ioctl.c | 44 +++++++++++++++++++++++++++------
drivers/nvme/host/nvme.h | 1 +
include/uapi/linux/nvme_ioctl.h | 1 +
4 files changed, 39 insertions(+), 8 deletions(-)
--
2.25.1
next parent reply other threads:[~2022-05-20 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220520050118epcas5p1f6a930419285ecdac65afaa22255c03f@epcas5p1.samsung.com>
2022-05-20 4:55 ` Kanchan Joshi [this message]
2022-05-20 4:55 ` [PATCH v2 1/2] nvme: helper for uring-passthrough checks Kanchan Joshi
2022-05-20 4:56 ` [PATCH v2 2/2] nvme: enable uring-passthrough for admin commands Kanchan Joshi
2022-05-20 6:01 ` [PATCH v2 0/2] " Christoph Hellwig
2022-05-20 8:21 ` Kanchan Joshi
2022-05-20 9:15 ` 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=20220520045600.3773-1-joshi.k@samsung.com \
--to=joshi.k@samsung.com \
--cc=axboe@kernel.dk \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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