public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Proposals to change the way all drivers work with SCSI commands
Date: Fri, 11 May 2007 16:10:29 -0400	[thread overview]
Message-ID: <4644CDB5.2070604@garzik.org> (raw)
In-Reply-To: <1178912975.3692.61.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Fri, 2007-05-11 at 15:15 -0400, Jeff Garzik wrote:
>> James Bottomley wrote:
>>> Right at the moment, we're planning to clean up the way SCSI drivers
>>> process commands.  The proposals are essentially:
>>>
>>>      1. Get rid of the now unnecessary map_single path (every command is
>>>         either zero transfer or scatter/gather)
>>>      2. use accessors to manipulate the SG lists (mainly so that we can
>>>         alter the implementation without affecting the drivers)
>>>
>>> It strikes me that in all of this, we could also consider doing the DMA
>>> mapping inside the mid layer (instead of in every driver).  This is
>>> essentially what libata is already doing ... leading to confusion in
>>> SCSI drivers that use libata for SATA.
>> My eyes are crossed :)  How does doing DMA mapping in the mid layer lead 
>> to confusion in SCSI drivers that use libata for SATA?  Are you talking 
>> about aic94xx and ipr only, or other drivers?
> 
> Those are the only two that use libata for SATA, yes.
> 
> aic94xx is horrible in this regard ... it has to try to distinguish STP
> commands that come from libsas (and thus aren't mapped) from ones that
> come from libata which are ... and it still doesn't get it entirely
> right.

I would lean towards fixing libata to -not- DMA-map for those drivers. 
Splitting up DMA mapping is ugly.

	Jeff




  reply	other threads:[~2007-05-11 20:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 18:33 Proposals to change the way all drivers work with SCSI commands James Bottomley
2007-05-11 18:42 ` FUJITA Tomonori
2007-05-11 19:15 ` Jeff Garzik
2007-05-11 19:49   ` James Bottomley
2007-05-11 20:10     ` Jeff Garzik [this message]
2007-05-11 20:00 ` David Miller
2007-05-11 21:12   ` James Bottomley
2007-05-11 21:21     ` David Miller
2007-05-11 21:36       ` James Bottomley
2007-05-11 21:47         ` David Miller
2007-05-11 21:52           ` James Bottomley
2007-05-11 21:20 ` Stefan Richter
2007-05-11 21:30   ` Kristian Høgsberg
2007-05-11 21:58     ` Stefan Richter
2007-05-12  6:35 ` Muli Ben-Yehuda
2007-05-12  9:12 ` Heiko Carstens
2007-05-12 13:04   ` James Bottomley
2007-05-12 15:29 ` Christoph Hellwig
2007-05-12 15:50   ` James Bottomley
2007-05-12 15:52     ` 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=4644CDB5.2070604@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox