From: Andy Grover <agrover@redhat.com>
To: target-devel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, hch@lst.de, nab@linux-iscsi.org,
shli@kernel.org, linux-kernel@vger.kernel.org, rjones@redhat.com
Subject: [PATCH 0/4] Userspace Passthrough backstore for LIO
Date: Mon, 15 Sep 2014 16:12:26 -0700 [thread overview]
Message-ID: <1410822750-10717-1-git-send-email-agrover@redhat.com> (raw)
Hi all,
Here is version three of the userspace passthrough backstore code I've
been working on. I think it's ready to be considered for upstream.
If you are wondering what this is, patch 3 is documentation that
should explain, at both a high- and low-level.
There are other pieces needed for this to work properly -- changes to
targetcli and rtslib to easily configure the new backstore type, plus
the user code that hooks up to the passthrough. I've written some code
to do this, called tcmu-runner
(https://github.com/agrover/tcmu-runner) but the userspace development
naturally is hindered until the kernel code is accepted :)
Changes since version 2:
* Incorporate doc improvements from Richard W. M. Jones
* Correct off-by-1 error in tcmu_get_blocks
* execute_rw must be set in the sbc_ops passed to sbc_parse_cdb
Thanks -- Andy
Andy Grover (4):
target: Remove unneeded check in sbc_parse_cdb
uio: Export definition of struct uio_device
target: Add documentation on the target userspace pass-through driver
target: Add a user-passthrough backstore
Documentation/target/tcmu-design.txt | 239 +++++++
drivers/target/Kconfig | 5 +
drivers/target/Makefile | 1 +
drivers/target/target_core_sbc.c | 2 +-
drivers/target/target_core_transport.c | 4 +
drivers/target/target_core_user.c | 1169 ++++++++++++++++++++++++++++++++
drivers/uio/uio.c | 12 -
include/linux/uio_driver.h | 12 +-
include/uapi/linux/Kbuild | 1 +
include/uapi/linux/target_core_user.h | 142 ++++
10 files changed, 1573 insertions(+), 14 deletions(-)
create mode 100644 Documentation/target/tcmu-design.txt
create mode 100644 drivers/target/target_core_user.c
create mode 100644 include/uapi/linux/target_core_user.h
--
1.9.3
next reply other threads:[~2014-09-15 23:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 23:12 Andy Grover [this message]
2014-09-15 23:12 ` [PATCH 1/4] target: Remove unneeded check in sbc_parse_cdb Andy Grover
2014-09-15 23:12 ` [PATCH 2/4] uio: Export definition of struct uio_device Andy Grover
2014-09-15 23:12 ` [PATCH 3/4] target: Add documentation on the target userspace pass-through driver Andy Grover
2014-09-15 23:12 ` [PATCH 4/4] target: Add a user-passthrough backstore Andy Grover
2014-09-19 21:14 ` Nicholas A. Bellinger
[not found] ` <lvi81j$ud8$2@ger.gmane.org>
2014-09-19 23:39 ` Nicholas A. Bellinger
2014-09-19 23:51 ` Alex Elsayed
2014-09-20 0:35 ` Andy Grover
2014-09-22 20:58 ` Nicholas A. Bellinger
2014-09-22 21:00 ` Andy Grover
2014-09-22 21:03 ` Nicholas A. Bellinger
2014-09-22 20:36 ` Nicholas A. Bellinger
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=1410822750-10717-1-git-send-email-agrover@redhat.com \
--to=agrover@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=rjones@redhat.com \
--cc=shli@kernel.org \
--cc=target-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).