public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: hch@lst.de, kbusch@kernel.org, axboe@kernel.dk,
	linux-nvme@lists.infradead.org, gost.dev@samsung.com,
	joshiiitr@gmail.com
Subject: Re: [PATCH 2/3] nvme: enable uring-passthrough for admin commands
Date: Tue, 17 May 2022 10:15:20 +0200	[thread overview]
Message-ID: <20220517081520.GA14308@lst.de> (raw)
In-Reply-To: <20220517053147.7925-3-joshi.k@samsung.com>

On Tue, May 17, 2022 at 11:01:46AM +0530, Kanchan Joshi wrote:
> Add a new opcode NVME_URING_CMD_ADMIN that userspace can use.
> Wire up support for the case when this is issued over generic char
> device node (/dev/ngXnY).

I would really prefer not adding this to the per-namespaces nodes.
The do something controller specific on the namespace node patter is
a massive pain both in terms of code and semantics.


  reply	other threads:[~2022-05-17  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220517053710epcas5p374ddc759e51f3adb243a5e98f5038699@epcas5p3.samsung.com>
2022-05-17  5:31 ` [PATCH 0/3] uring-passthrough for admin commands Kanchan Joshi
2022-05-17  5:31   ` [PATCH 1/3] nvme: helper for uring-passthrough checks Kanchan Joshi
2022-05-17  8:15     ` Christoph Hellwig
2022-05-17  5:31   ` [PATCH 2/3] nvme: enable uring-passthrough for admin commands Kanchan Joshi
2022-05-17  8:15     ` Christoph Hellwig [this message]
2022-05-17 13:50       ` Kanchan Joshi
2022-05-18  7:29         ` Christoph Hellwig
2022-05-19  9:52           ` Kanchan Joshi
2022-05-17  5:31   ` [PATCH 3/3] nvme: admin command uring-passthrough on controller node Kanchan Joshi

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=20220517081520.GA14308@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=gost.dev@samsung.com \
    --cc=joshi.k@samsung.com \
    --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