linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@suse.de>,
	John Chandy <john.chandy@uconn.edu>,
	open-osd <osd-dev@open-osd.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 4/4] libosd: write/read_sg_kern API
Date: Tue, 02 Nov 2010 10:33:31 +0200	[thread overview]
Message-ID: <4CCFCCDB.8060406@panasas.com> (raw)
In-Reply-To: <20101101161329.GA24836@infradead.org>

On 11/01/2010 06:13 PM, Christoph Hellwig wrote:
> On Tue, Oct 19, 2010 at 02:22:42PM +0200, Boaz Harrosh wrote:
>> From: John A. Chandy <john.chandy@uconn.edu>
>>
>> This is a trivial addition to the SG API that can receive kernel
>> pointers. It is only used by the out-of-tree test module. So
>> it's immediate need is questionable. For maintenance ease it might
>> just get in, as it's very small.
>>
>> John.
>> do you need this in the Kernel, or is it only for osd_ktest.ko?
> 
> It really shouldn't be in the tree at all. s/g lists are not something
> that should be passed to a logical I/O layer.
> 

Please read the patch ;-)
It has been asked before, these are not Linux Kernel sg(s). These are
OSD scatter-gather. Osd scatter-gather are an array of extents
[offset, length] to which to write/read to/from in the object. The
memory buffer information is the same as a simple write/read. Only
that the target will random-seek+fetch bytes in a single on-the-wire
IO. There exist the same command for SCSI-disk targets as well.

I know that the conceptual name means something else, and I should have
perhaps chosen a new name. But the STD calls it Scatter-Gather and I have
not yet invented any new names, and always used the STD names for things.
It is not until people got mixed up that I realized it might have been
a mistake to call it that.

Should I submit a patch that renames anything "sg" to "extents", or some
other name? (Please note, there is no name collision it is all osd_sg_xxx)

Thanks
Boaz

      reply	other threads:[~2010-11-02  8:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 12:18 [PATCHSET 0/4] libosd: scatter gather commands and stuff for 2.6.37 Boaz Harrosh
2010-10-19 12:20 ` [PATCH 1/4] libosd: Fix bug in attr_page handling Boaz Harrosh
2010-10-19 12:21 ` [PATCH 2/4] libosd: Free resources in reverse order of allocation Boaz Harrosh
2010-10-19 12:22 ` [PATCH 3/4] libosd: Support for scatter gather write/read commands Boaz Harrosh
2010-10-19 12:22 ` [PATCH 4/4] libosd: write/read_sg_kern API Boaz Harrosh
2010-10-19 14:13   ` Boaz Harrosh
2010-10-19 14:13   ` [PATCH 4/4 ver2] " Boaz Harrosh
2010-10-22 17:32     ` Vladislav Bolkhovitin
2010-10-24  9:55       ` Boaz Harrosh
2010-10-25 18:50         ` Vladislav Bolkhovitin
2010-10-26 10:07           ` Boaz Harrosh
2010-10-20 14:28   ` [PATCH 4/4] " John Chandy
2010-10-21 12:13     ` Boaz Harrosh
2010-11-01 16:13   ` Christoph Hellwig
2010-11-02  8:33     ` Boaz Harrosh [this message]

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=4CCFCCDB.8060406@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@suse.de \
    --cc=hch@infradead.org \
    --cc=john.chandy@uconn.edu \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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).