public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.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: Sat, 12 May 2007 16:29:16 +0100	[thread overview]
Message-ID: <20070512152916.GA7992@infradead.org> (raw)
In-Reply-To: <1178908422.3692.58.camel@mulgrave.il.steeleye.com>

On Fri, May 11, 2007 at 01:33:41PM -0500, 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.
> 
> So what do people think about this?

I don't like it at all.  It means we tange up dma mapping bits into
a layer were they don't belong at all.  We have hbas doing pio, doing
channel programs, mangling dma list before or after the mapping or just
dealing with the commands in kernelspace.  We also have architectures
without dma mapping support.

I'd rather give the drivers proper helpers as in tomo's proposal and
let them handle what should be in their layer.

Btw, Adam Richter already sent a patch doing the dma mapping in
scsi.c back in 2002 and he got shot down for the same reasons, although
I can't find the arguments in the list archives anymore.

  parent reply	other threads:[~2007-05-12 15:29 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
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 [this message]
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=20070512152916.GA7992@infradead.org \
    --to=hch@infradead.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