All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: Kai.Makisara@kolumbus.fi, linux-scsi@vger.kernel.org
Subject: Re: [PATCH, RFC] st: start using scsi_execute
Date: Mon, 30 Jan 2006 15:45:35 -0600	[thread overview]
Message-ID: <43DE88FF.60102@cs.wisc.edu> (raw)
In-Reply-To: <20060130182324.GA6253@lst.de>

Christoph Hellwig wrote:
> This patch updates st to use scsi_execute instead of scsi_execute_async
> for all scsi commands except the main I/O path.  The advantage is that
> these helpers do all the request tracking for these synchronous I/Os so
> that there is no need for st_request structures.  It also decouples
> these helper scsi commands from the main tape buffer, allowing for an
> easier switchover to the generic block request mapping routines for the
> main I/O path later on.
> 

I guess I messed that up. I am not sure why I went with 
scsi_execute_async for st.

But in my past attempts to convert these drivers to the block layer I 
was trying to make some nice function like scsi_execute and friends 
where the ULD does not have to worry about setting up any structure. 
Instead, we could have st and sg use the block layer functions directly 
like how block/scsi_ioct.c does. So the ULD would get a request, fill 
out the necessary fields, call blk_rq_map_user and call blk_execute*. Is 
is better to have a scsi API that sets things up for the ULDs or is the 
abstraction not worth it?

  parent reply	other threads:[~2006-01-30 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 18:23 [PATCH, RFC] st: start using scsi_execute Christoph Hellwig
2006-01-30 21:19 ` Kai Makisara
2006-01-30 21:36   ` Mike Christie
2006-01-30 21:45 ` Mike Christie [this message]
2006-02-04 10:41 ` Kai Makisara

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=43DE88FF.60102@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=hch@lst.de \
    --cc=linux-scsi@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.