public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: 'James Bottomley' <James.Bottomley@SteelEye.com>,
	'Douglas Gilbert' <dougg@torque.net>,
	'Mike Christie' <michaelc@cs.wisc.edu>,
	'device-mapper development' <dm-devel@redhat.com>,
	'linux-scsi' <linux-scsi@vger.kernel.org>,
	LIRANS@il.ibm.com
Subject: Re: [PATCH RFC 0/4] use scatter lists for all blockpc	requests	and simplify hw handlers
Date: Tue, 7 Jun 2005 20:43:36 +0200	[thread overview]
Message-ID: <20050607184335.GD8172@suse.de> (raw)
In-Reply-To: <007e01c56b90$1a09a6f0$e0019d89@cybernetics.com>

On Tue, Jun 07 2005, Tony Battersby wrote:
> > > My company (Cybernetics) sells several products that run embedded
> Linux
> > > which use the userspace scatter-gather capability of the SG driver.
> > > They are still running the 2.4 kernel series, but we will probably
> > > switch to 2.6 at some point.
> >
> > What do they actually use it for?  As in why is the data scattered
> even
> > in the virtual address space?
> 
> One of our products is a RAID-like controller for SCSI tape drives.
> Parallel SCSI or iSCSI in via a target-mode SCSI driver and parallel
> SCSI, iSCSI, or FC out via the SG driver, with various functions in
> between for data buffering, emulation, striping, mirroring, etc.  The
> program that controls everything has a complex internal buffering scheme
> that uses userspace scatter-gather for the main read/write I/O path to
> the tape drives.

That sounds like a valid use. Either way, I don't think we should remove
such a feature. It's a sane feature, and people might be using it -
there's no excuse for removing it.
Should we kill readv next? :)

-- 
Jens Axboe


  reply	other threads:[~2005-06-07 18:42 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04  1:19 [PATCH RFC 0/4] use scatter lists for all block pc requests and simplify hw handlers Mike Christie
2005-06-04 16:07 ` James Bottomley
2005-06-05  7:15   ` Mike Christie
2005-06-05  9:41     ` [dm-devel] " christophe varoqui
2005-06-06 13:31       ` Lars Marowsky-Bree
2005-06-07  0:04         ` Michael Christie
2005-06-07  7:01           ` [dm-devel] " Lars Marowsky-Bree
2005-06-05 14:40     ` James Bottomley
2005-06-05 19:11       ` James Bottomley
2005-06-06  5:43         ` Douglas Gilbert
2005-06-06 14:19           ` James Bottomley
2005-06-07 13:08             ` Douglas Gilbert
2005-06-07 13:34               ` Tony Battersby
2005-06-07 16:34                 ` James Bottomley
2005-06-07 18:38                   ` [PATCH RFC 0/4] use scatter lists for all blockpc " Tony Battersby
2005-06-07 18:43                     ` Jens Axboe [this message]
2005-06-07 15:59               ` [PATCH RFC 0/4] use scatter lists for all block pc " James Bottomley
2005-06-07 18:07                 ` Jens Axboe
2005-06-07 19:26                   ` James Bottomley
2005-06-08  7:09                     ` Jens Axboe
2005-06-06 19:02     ` Patrick Mansfield
2005-06-07 15:26       ` Michael Christie
2005-06-07 18:23         ` Patrick Mansfield
2005-06-08 15:41           ` Mike Christie
2005-06-09  0:08             ` Patrick Mansfield
2005-06-09  6:18               ` Jens Axboe
2005-06-09 11:51                 ` James Bottomley
2005-06-09 11:54                   ` Jens Axboe
2005-06-07 12:10   ` Christoph Hellwig
2005-06-07 12:20     ` James Bottomley
2005-06-07 15:36       ` Michael Christie
2005-06-07 15:45         ` [dm-devel] " Michael Christie
2005-06-07 16:26           ` Kai Makisara
2005-06-07 19:23             ` James Bottomley
2005-06-07 18:09         ` Jens Axboe
2005-06-08 12:46           ` Mike Christie
2005-06-07 18:07 ` Jens Axboe
2005-06-07 19:38   ` James Bottomley
2005-06-08  3:00     ` Douglas Gilbert
2005-06-08 12:59       ` James Bottomley
2005-06-08 14:50         ` Luben Tuikov

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=20050607184335.GD8172@suse.de \
    --to=axboe@suse.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=LIRANS@il.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=tonyb@cybernetics.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