From: "hch@lst.de" <hch@lst.de>
To: Clay Mayers <Clay.Mayers@kioxia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"javier@javigon.com" <javier@javigon.com>,
"anuj20.g@samsung.com" <anuj20.g@samsung.com>,
"joshiiitr@gmail.com" <joshiiitr@gmail.com>,
"pankydev8@gmail.com" <pankydev8@gmail.com>
Subject: Re: [RFC 02/13] nvme: wire-up support for async-passthru on
Date: Wed, 22 Dec 2021 09:02:20 +0100 [thread overview]
Message-ID: <20211222080220.GA21346@lst.de> (raw)
In-Reply-To: <2da62822fd56414d9893b89e160ed05c@kioxia.com>
On Tue, Dec 21, 2021 at 09:16:27PM +0000, Clay Mayers wrote:
> Message-ID: <20211220141734.12206-3-joshi.k@samsung.com>
>
> On 12/20/21 19:47:23 +0530, Kanchan Joshi wrote:
> > Introduce handlers for fops->async_cmd(), implementing async passthru on
> > char device (including the multipath one).
> > The handlers supports NVME_IOCTL_IO64_CMD.
> >
> I commented on these two issues below in more detail at
> https://github.com/joshkan/nvme-uring-pt/issues
If you want people to read your comments send them here and not on some
random website no one is reading.
next prev parent reply other threads:[~2021-12-22 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 21:16 [RFC 02/13] nvme: wire-up support for async-passthru on Clay Mayers
2021-12-22 8:02 ` hch [this message]
2021-12-22 15:11 ` Clay Mayers
2021-12-22 13:46 ` 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=20211222080220.GA21346@lst.de \
--to=hch@lst.de \
--cc=Clay.Mayers@kioxia.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=javier@javigon.com \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pankydev8@gmail.com \
/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