linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/4] aic7xxx: Enable 16-bit CDBs
Date: Thu, 25 Oct 2007 08:31:17 +0200	[thread overview]
Message-ID: <47203835.30404@suse.de> (raw)
In-Reply-To: <1193158612.6294.9.camel@localhost.localdomain>

James Bottomley wrote:
> On Mon, 2007-10-22 at 13:57 +0200, Hannes Reinecke wrote:
>> Matthew Wilcox wrote:
>>> On Mon, Oct 22, 2007 at 08:50:45AM +0200, Hannes Reinecke wrote:
>>>> That's what I thought, too. Hence the patch.
>>>> But if we set the default to 16 byte cdbs you can of course ignore
>>>> the patch.
>>> I think the comment in hosts.c explains why we shouldn't do that ...
>>>
>> _I_ certainly wouldn't. But if the maintainer says so :-)
> 
> Actually, I misremembered.  I thought I did a commit a few years ago
> that automatically raised the cutoff to 16 byte cdbs and forced drivers
> who couldn't do that to lower the limit, but apparently it was never
> merged.
> 
> So, just pick either 16 or 32 for both drivers and add that as the max
> cdb size.
> 
Hmm. But aic7xxx actually supports 32-byte cdbs (for whatever reason);
cf drivers/scsi/aic7xxx/aic7xxx.h:478.
And aic79xx only supports 16 byte cdbs; the clever 'use pointer for cdb
if it's longer than the 12 bytes' routine sadly isn't implemented
for aic79xx.

It somehow feels wrong to arbitrarily cut the limit to 16 bytes for
aic7xxx, hence the two different limits.

But again, you're the maintainer, you get to decide.
If you feel it's reasonable to limit both to 16 byte so be it.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-10-25  6:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  8:32 [PATCH 4/4] aic7xxx: Enable 16-bit CDBs Hannes Reinecke
2007-10-21 16:19 ` James Bottomley
2007-10-22  3:46   ` Matthew Wilcox
2007-10-22  6:50     ` Hannes Reinecke
2007-10-22 11:23       ` Matthew Wilcox
2007-10-22 11:57         ` Hannes Reinecke
2007-10-23 16:56           ` James Bottomley
2007-10-25  6:31             ` Hannes Reinecke [this message]
2007-10-22 19:10   ` Boaz Harrosh
2007-10-22 19:35     ` Matthew Wilcox
2007-10-22 21:24       ` Benny Halevy

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=47203835.30404@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).