public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: [PATCH 0/2] nvme: support I/O passthrough for multipath
Date: Sun, 14 Feb 2021 20:01:24 +0900	[thread overview]
Message-ID: <20210214110126.24023-1-minwoo.im.dev@gmail.com> (raw)

Hello,

This series is to support I/O passthrough for multipath I/O.

Currently driver exposes block device for the head namespace.  Also, the
path will be decided by the driver with the I/O policy defined to the
actual hidden device based on ANA state.  This means that userspace is not
allowed to I/O passthrough to a specified namespace target which is hidden
by the driver.

This series is to support passthrough to the namespace attached to a
controller regardless to ANA state (e.g., inaccessible) and decided path
by the driver.

Please review.

Thanks,

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2021-02-14 11:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 11:01 Minwoo Im [this message]
2021-02-14 11:01 ` [PATCH] nvme: introduce passthrough ioctl for multipath Minwoo Im
2021-02-15 17:02   ` Keith Busch
2021-02-16  9:51     ` Minwoo Im
2021-02-16 17:57       ` Keith Busch
2021-02-17  2:14         ` Minwoo Im
2021-02-18  8:40           ` Christoph Hellwig
2021-02-18  8:48             ` Javier González
2021-02-19 21:27               ` Minwoo Im
2021-02-19 21:26             ` Minwoo Im
2021-02-14 11:01 ` [nvme-cli PATCH] nvme: add [--mpath|-M] option to io-passthru Minwoo Im

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=20210214110126.24023-1-minwoo.im.dev@gmail.com \
    --to=minwoo.im.dev@gmail.com \
    --cc=axboe@fb.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