All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
	hch@lst.de, nab@linux-iscsi.org, shli@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/2] target: Add documentation on the target userspace pass-through driver
Date: Tue, 02 Sep 2014 15:06:14 -0700	[thread overview]
Message-ID: <54063F56.9090606@redhat.com> (raw)
In-Reply-To: <20140831212257.GO1302@redhat.com>

On 08/31/2014 02:22 PM, Richard W.M. Jones wrote:
> Reading this several times, I now think I get what it's trying to say,
> but I think it needs to introduces the terms (as the Economist style
> does).  Something like this:
>
>    "TCM is the new name for LIO, an in-kernel iSCSI target (server).
>    Existing TCM targets run in the kernel.  TCMU (TCM in Userspace)
>    allows userspace programs to be written which act as iSCSI targets.
>    This document describes the design.
>
>    The existing kernel provides modules for different SCSI transport
>    protocols.  TCM also modularizes the data storage.  There are
>    existing modules for file, block device, RAM or using another SCSI
>    device as storage.  These are called "backstores" or "storage
>    engines".  These built-in modules are implemented entirely as kernel
>    code."
>
> And hopefully having defined a bit of background, the rest of the
> document just flows nicely:

Thanks much! I've put this in the doc, and will hopefully send out a 
final patchset for inclusion with the new text in the next week or so.

<begin naming potential-bikeshed wasteoftime>

The only change I made was "another" instead of "the new name" -- 
because to be honest I don't know if there was actually an attempt at a 
name change, and if so if it was successful or not :) LIO seems to have 
stuck, but TCM seems to refer just to the "backend" part of LIO.

<end bikeshed>

Thanks again -- Andy

  reply	other threads:[~2014-09-02 22:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 19:11 [RFC 0/2] target: userspace pass-through backend Andy Grover
2014-07-01 19:11 ` [RFC 1/2] target: Add documentation on the target userspace pass-through driver Andy Grover
2014-07-05 11:29   ` Alex Elsayed
2014-07-08 22:03     ` Andy Grover
2014-08-30 17:35   ` Richard W.M. Jones
2014-08-31 19:49     ` Andy Grover
2014-08-31 21:22       ` Richard W.M. Jones
2014-09-02 22:06         ` Andy Grover [this message]
2014-07-01 19:11 ` [RFC 2/2] target: Add a user-passthrough backstore Andy Grover
2014-07-07 21:26 ` [RFC 0/2] target: userspace pass-through backend Andy Grover
2014-07-14 15:08 ` Stefan Hajnoczi
2014-08-20 18:28 ` [RFCv2 0/4] Userspace pass-through storage engine (backend) Andy Grover
2014-08-20 18:28   ` [RFCv2 1/4] target: Remove unneeded check in sbc_parse_cdb Andy Grover
2014-08-20 18:28   ` [RFCv2 2/4] uio: Export definition of struct uio_device Andy Grover
2014-08-20 18:28   ` [RFCv2 3/4] target: Add a user-passthrough backstore Andy Grover
2014-08-20 18:28   ` [RFCv2 4/4] target: Add documentation on the target userspace pass-through driver Andy Grover

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=54063F56.9090606@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.