public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
	Kanchan Joshi <joshi.k@samsung.com>,
	io-uring@vger.kernel.org, linux-nvme@lists.infradead.org,
	asml.silence@gmail.com, ming.lei@redhat.com, mcgrof@kernel.org,
	shr@fb.com, joshiiitr@gmail.com, anuj20.g@samsung.com,
	gost.dev@samsung.com
Subject: Re: [PATCH v4 4/5] nvme: wire-up uring-cmd support for io-passthru on char-device.
Date: Fri, 6 May 2022 10:28:44 +0200	[thread overview]
Message-ID: <20220506082844.GA30405@lst.de> (raw)
In-Reply-To: <8ae2c507-ffcc-b693-336d-2d9f907edb76@kernel.dk>

On Thu, May 05, 2022 at 11:23:01AM -0600, Jens Axboe wrote:
> The top three patches here have a proposed solution for the 3 issues
> that I highlighted:
> 
> https://git.kernel.dk/cgit/linux-block/log/?h=for-5.19/io_uring-passthrough
> 
> Totally untested... Kanchan, can you take a look and see what you think?
> They all need folding obviously, I just tried to do them separately.
> Should also get tested :-)

I've also pushed out a tree based on this, which contains my little
fixups that I'd suggest to be folded.  Totally untested and written
while jetlagged:

http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/io_uring-passthrough

Note that while I tried to keep all my changes in separate patches, the
main passthrough patch had conflicts during a rebase, which I had to
fix up, but I tried to touch as little as possible.


  reply	other threads:[~2022-05-06  8:30 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220505061142epcas5p2c943572766bfd5088138fe0f7873c96c@epcas5p2.samsung.com>
2022-05-05  6:06 ` [PATCH v4 0/5] io_uring passthrough for nvme Kanchan Joshi
2022-05-05  6:06   ` [PATCH v4 1/5] fs,io_uring: add infrastructure for uring-cmd Kanchan Joshi
2022-05-05 12:52     ` Jens Axboe
2022-05-05 13:48       ` Ming Lei
2022-05-05 13:54         ` Jens Axboe
2022-05-05 13:29     ` Christoph Hellwig
2022-05-05 16:17     ` Jens Axboe
2022-05-05 17:04       ` Jens Axboe
2022-05-06  7:12       ` Kanchan Joshi
2022-05-10 14:23       ` Kanchan Joshi
2022-05-10 14:35         ` Jens Axboe
2022-05-05  6:06   ` [PATCH v4 2/5] block: wire-up support for passthrough plugging Kanchan Joshi
2022-05-05 14:21     ` Ming Lei
2022-05-05  6:06   ` [PATCH v4 3/5] nvme: refactor nvme_submit_user_cmd() Kanchan Joshi
2022-05-05 13:30     ` Christoph Hellwig
2022-05-05 18:37     ` Clay Mayers
2022-05-05 19:03       ` Jens Axboe
2022-05-05 19:11         ` Jens Axboe
2022-05-05 19:30           ` Clay Mayers
2022-05-05 19:31             ` Jens Axboe
2022-05-05 19:50               ` hch
2022-05-05 20:44                 ` Jens Axboe
2022-05-06  5:56                   ` hch
2022-05-05  6:06   ` [PATCH v4 4/5] nvme: wire-up uring-cmd support for io-passthru on char-device Kanchan Joshi
2022-05-05 13:33     ` Christoph Hellwig
2022-05-05 13:38     ` Jens Axboe
2022-05-05 13:42       ` Christoph Hellwig
2022-05-05 13:50         ` Jens Axboe
2022-05-05 17:23           ` Jens Axboe
2022-05-06  8:28             ` Christoph Hellwig [this message]
2022-05-06 13:37               ` Jens Axboe
2022-05-06 14:50                 ` Christoph Hellwig
2022-05-06 14:57                   ` Jens Axboe
2022-05-07  5:03                     ` Christoph Hellwig
2022-05-07 12:53                       ` Jens Axboe
2022-05-09  6:00                         ` Christoph Hellwig
2022-05-09 12:52                           ` Jens Axboe
2022-05-05  6:06   ` [PATCH v4 5/5] nvme: add vectored-io support for uring-cmd Kanchan Joshi
2022-05-05 18:20   ` [PATCH v4 0/5] io_uring passthrough for nvme Jens Axboe
2022-05-05 18:29     ` Jens Axboe
2022-05-06  6:42       ` Kanchan Joshi
2022-05-06 13:14         ` Jens Axboe
2022-05-10  7:20     ` Christoph Hellwig
2022-05-10 12:29       ` Jens Axboe
2022-05-10 14:21         ` 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=20220506082844.GA30405@lst.de \
    --to=hch@lst.de \
    --cc=anuj20.g@samsung.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=gost.dev@samsung.com \
    --cc=io-uring@vger.kernel.org \
    --cc=joshi.k@samsung.com \
    --cc=joshiiitr@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=shr@fb.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