All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH RFC/RFT 2/4] add scsi helpers
Date: Thu, 15 Sep 2005 12:55:18 -0500	[thread overview]
Message-ID: <4329B586.6010802@cs.wisc.edu> (raw)
In-Reply-To: <4329AF9F.1030209@cs.wisc.edu>

Mike Christie wrote:
>>
>>
>>> +int scsi_execute_async_iov_req(struct scsi_device *sdev,
>>> +                   const unsigned char *cmd, int data_direction,
>>> +                   struct kvec *vec, int vec_count, int timeout,
>>> +                   int retries, void *privdata,
>>> +                   void (*done)(void *, char *, int, int))
>>
>>
>>
>> If you passed an request_queue_t instead of th scsi_device this function
>> would not have any knowledge about scsi internals and could be moved up
>> to the block layer.  not sure that's actually a good idea.
> 
> 
> Did you want to move scsi_execute too?
> 

Actually after talking with Jens, I think it is better to keep the 
function in scsi_lib and move my blk_rq_map_iov() function there. The 
problem is that sg and st have some special needs and as a result do 
some things like partial setup themselves. It looks like nobody wants 
the burdon of having these special case fucntions :) but since SCSI's 
ULDs are the only user and probably will be the only user does it make 
sense to keep them there?

  reply	other threads:[~2005-09-15 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 22:19 [PATCH RFC/RFT 2/4] add scsi helpers Mike Christie
2005-09-15 10:13 ` Christoph Hellwig
2005-09-15 17:30   ` Mike Christie
2005-09-15 17:55     ` Mike Christie [this message]
2005-09-15 18:29       ` Christoph Hellwig

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=4329B586.6010802@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=hch@infradead.org \
    --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.