linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: ak@muc.de
Cc: Rik van Riel <riel@redhat.com>,
	Luben Tuikov <luben_tuikov@adaptec.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Sun, 11 Sep 2005 08:41:10 -0500	[thread overview]
Message-ID: <1126446071.4831.5.camel@mulgrave> (raw)
In-Reply-To: <20050911035621.87661.qmail@mail.muc.de>

On Sun, 2005-09-11 at 05:56 +0200, ak@muc.de wrote:
> >> Naturally, aic94xx has _no limitations_. :-)  But hey, our hardware just 
> >> kicks a*s!
> >
> > That's very nice for you - but lets face it, a SAS layer
> > that'll be unable to also deal with the El-Cheapo brand
> > controllers isn't going to be very useful.
> 
> Nobody knows what these bu^wlimitations will be though. So you cannot
> really plan for them in advance.  When someone writes drivers for such 
> limited hardware they can add code to handle the limitations. But it 
> seems reasonable to start with a clean hardware model, and only
> add the hacks later when they are really needed and the requirements
> are understood.

But my point was that we already have a mechanism for coping with this:
The scsi template parameterises some of these things (max sector size,
sg table elements, clustering, etc).  For less standard things it
doesn't cover the driver uses the blk_ adjustors directly from
slave_alloc/slave_configure (This is currently how USB and firewire
communicate their alignment requirements).

By wrappering both the template and the slave_alloc/slave_configure
methods in the SAS class and not providing the driver access, it can't
use existing methods to make any adjustments that may be necessary.

James



  reply	other threads:[~2005-09-11 13:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:42 [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Luben Tuikov
2005-09-09 23:35 ` James Bottomley
2005-09-10  4:12   ` Luben Tuikov
2005-09-10 13:08     ` Arjan van de Ven
2005-09-12 13:55       ` Luben Tuikov
2005-09-12 14:13         ` Jörn Engel
2005-09-12 18:46           ` Luben Tuikov
2005-09-12 18:46       ` Luben Tuikov
2005-09-10 14:30     ` Rik van Riel
2005-09-10 20:20       ` Alan Cox
2005-09-11  9:40         ` Christoph Hellwig
2005-09-13 12:41           ` Luben Tuikov
2005-09-11  3:56       ` ak
2005-09-11 13:41         ` James Bottomley [this message]
2005-09-12 17:12           ` Luben Tuikov
2005-09-12 17:55             ` Alan Cox
2005-09-12 13:56       ` Luben Tuikov
2005-09-11  9:38     ` Christoph Hellwig
2005-09-12 16:08       ` Matthew Wilcox
2005-09-12 19:07         ` Luben Tuikov
2005-09-12 19:55           ` Matthew Wilcox
2005-09-12 23:51             ` Stefan Richter
2005-09-12 22:00       ` Luben Tuikov
2005-09-13 15:40         ` Matthew Wilcox
2005-09-14  5:56           ` Sergey Panov
2005-09-14 10:37             ` Christoph Hellwig
2005-09-14 10:53             ` Jeff Garzik
2005-09-14 12:59               ` Luben Tuikov

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=1126446071.4831.5.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luben_tuikov@adaptec.com \
    --cc=riel@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).