public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@suse.de>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi@vger.kernel.org
Subject: Re: Aic7xxx v6.2.22 and Aic79xx v1.3.0Alpha2 Released
Date: Fri, 13 Dec 2002 21:06:43 +0000	[thread overview]
Message-ID: <20021213210643.B15074@infradead.org> (raw)
In-Reply-To: <20021212173818.GA6481@suse.de>; from axboe@suse.de on Thu, Dec 12, 2002 at 06:38:18PM +0100

On Thu, Dec 12, 2002 at 06:38:18PM +0100, Jens Axboe wrote:
> > 1) You have to set a flag when you've already told the system you
> >    dma capabilities.
> 
> All drivers blindly copy the setting of the dma mask, typically means
> nothing.

Maybe it's a bit to dangerous for 2.4, but for 2.5 Justin's suggestion
looks very nice, IMHO.


> > 2) That flag is not documented in hosts.h or in the Documentation directory.
> 
> That is true. Name of the member is a good clue, though.

Hmm, actually I documented it at some point, I just can't remember
in what tree that was..

> > 4) highio requires that all SCSI drivers support single length S/G lists,
> >    but since single buffers are still allowed by the interfaces, even
> >    compliant SCSI drivers cannot strip out this code.
> 
> This is not a new requirement, it's just spelled out now. The special
> casing of an sg request with one entry was silly, imho. And yes you do
> have to support both single entry sg requests and non-sg requests. I
> wouldn't mind getting rid of that, but this is the 2.4 series and
> changes must be kept small(ish).

IIRC Alan planned to kill non-sg requests for 2.5.  But I don't know how
far he got.


  reply	other threads:[~2002-12-13 21:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 23:53 Aic7xxx v6.2.22 and Aic79xx v1.3.0Alpha2 Released Justin T. Gibbs
2002-12-10  0:12 ` Christoph Hellwig
2002-12-10  0:33   ` Justin T. Gibbs
2002-12-10 13:14     ` Christoph Hellwig
2002-12-10 16:02       ` James Bottomley
2002-12-10 20:03         ` Justin T. Gibbs
2002-12-10 20:58           ` James Bottomley
     [not found]         ` <20021211135855.A19325@infradead.org>
2002-12-11 15:18           ` Justin T. Gibbs
2002-12-11 15:39             ` Christoph Hellwig
2002-12-11 16:08               ` Justin T. Gibbs
2002-12-11 16:23                 ` Christoph Hellwig
2002-12-12  7:16                   ` Jens Axboe
2002-12-12 17:20                     ` Justin T. Gibbs
2002-12-12 17:38                       ` Jens Axboe
2002-12-13 21:06                         ` Christoph Hellwig [this message]
2002-12-14 10:42                           ` Jens Axboe
2002-12-11 17:06                 ` Alan Cox
2002-12-11 17:31               ` Justin T. Gibbs
2002-12-11 18:17                 ` Christoph Hellwig
2002-12-11 20:23                   ` Justin T. Gibbs
2002-12-12 20:20                   ` Doug Ledford
2002-12-12 20:39                     ` Christoph Hellwig
2002-12-12 21:06                     ` Justin T. Gibbs
2002-12-13 21:02                     ` Christoph Hellwig
2002-12-13 21:23                       ` Doug Ledford
2002-12-13 21:37                         ` Justin T. Gibbs
2002-12-13 21:51                         ` Christoph Hellwig
2002-12-13 22:52                           ` Doug Ledford
2002-12-13 23:08                             ` Justin T. Gibbs
2002-12-13 23:20                               ` Doug Ledford
2002-12-13 23:32                                 ` Justin T. Gibbs
2002-12-14 21:55               ` Gérard Roudier
2002-12-14 23:29                 ` Justin T. Gibbs
2002-12-19 18:56                   ` scsi_scan.c complaints Doug Ledford
2002-12-21  1:29                     ` Doug Ledford
2002-12-12  5:51         ` Aic7xxx v6.2.22 and Aic79xx v1.3.0Alpha2 Released Andrew Morton
2002-12-12 14:51           ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14  5:57 Milton D. Miller II

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=20021213210643.B15074@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=axboe@suse.de \
    --cc=gibbs@scsiguy.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