From: Matthew Wilcox <matthew@wil.cx>
To: Ingo Flaschberger <if@xip.at>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch
Date: Thu, 30 Mar 2006 09:24:29 -0700 [thread overview]
Message-ID: <20060330162429.GI13590@parisc-linux.org> (raw)
In-Reply-To: <Pine.GSO.4.64.0603301523130.6412@filebunker.xip.at>
On Thu, Mar 30, 2006 at 04:20:25PM +0200, Ingo Flaschberger wrote:
> >> {"CNSi", "G8324", NULL, BLIST_SPARSELUN}, /* Chaparral G8324
> >> RAID */
> >>+ {"COMPAQ", "ARRAY CONTROLLER", "2.60", BLIST_SPARSELUN |
> >>BLIST_LARGELUN |
> >>+ BLIST_MAX_512K}, /* Compaq RA4x00 */
> >>+ {"COMPAQ", "LOGICAL VOLUME", "2.60", BLIST_MAX_512K}, /* Compaq
> >>RA4x00 */
> >> {"COMPAQ", "LOGICAL VOLUME", NULL, BLIST_FORCELUN},
> >
> >I wonder if you should just be adding BLIST_MAX_512K to the current
> >entry for LOGICAL VOLUME instead?
>
> The "LOGICAL VOLUME" was there before and I think I will break the SCSI
> Version.
I meant to do something like:
- {"COMPAQ", "LOGICAL VOLUME", NULL, BLIST_FORCELUN},
+ {"COMPAQ", "LOGICAL VOLUME", NULL, BLIST_FORCELUN | BLIST_MAX_512K},
> >I'm not sure that's what you meant to do, even. How about more simply:
> >
> > /*
> > * Only support SCSI-3 and up devices if BLIST_NOREPORTLUN is not
> > set.
> > * Also allow SCSI-2 and unknown devices if BLIST_REPORTLUN2 is set
> > * and host adapter supports more than 8 LUNs.
> > */
> > if ((bflags & BLIST_NOREPORTLUN)
> > return 1;
> > if ((starget->scsi_level < SCSI_2) &&
> > (starget->scsi_level != SCSI_UNKNOWN))
> > return 1;
> > if ((starget->scsi_level < SCSI_3) &&
> > (!(bflags & BLIST_REPORTLUN2) || shost->max_lun <=
> > 8))
> > return 1;
> >
> >
>
> Attached,, new patch version 3....
> --- linux-2.6.16_org/drivers/scsi/scsi.c 2006-03-20 06:53:29.000000000 +0100
> +++ linux-2.6.16/drivers/scsi/scsi.c 2006-03-30 17:29:26.000000000 +0200
> @@ -567,7 +567,7 @@
> /*
> * If SCSI-2 or lower, store the LUN value in cmnd.
> */
> - if (cmd->device->scsi_level <= SCSI_2) {
> + if ((cmd->device->scsi_level <= SCSI_2) && (cmd->device->scsi_level != SCSI_UNKNOWN)) {
Oh, could you break the line so it doesn't go over 80 columns?
> sdev->select_no_atn = 1;
>
> /*
> + * Maximum 512K cdb transfer length
> + * broken RA4x00 Compaq Disk Array
> + */
> + sdev->max_xfer_len = 0xffff;
> + if (*bflags & BLIST_MAX_512K) {
> + sdev->max_xfer_len = 0x200;
> + }
Do we need the comment? We don't need the braces.
> + if (starget->scsi_level < SCSI_3 &&
> + ((!(bflags & BLIST_REPORTLUN2) &&
> + (starget->scsi_level != SCSI_UNKNOWN)) ||
> + shost->max_lun <= 8))
Why do we need the SCSI_UNKNOWN check here?
> * Support 32k/1M disks.
> + * - Added Compaq RA4x00 Fiber Channel Array support, 29.03.2006
> + * crossip communications gmbh - Ingo Flaschberger <if@xip.at>
> *
This doesn't really describe what you've done to this file. It's more
- Limit maximum transfers to new field in scsi_device
... or something
> @@ -89,6 +89,7 @@
> * scsi_devinfo.[hc]. For now used only to
> * pass settings from slave_alloc to scsi
> * core. */
> + unsigned short max_xfer_len; /* Maximum xfer length in one cdb */
> unsigned writeable:1;
> unsigned removable:1;
> unsigned changed:1; /* Data invalid due to media change */
I think you missed my point about where to place it -- due to padding
rules, you've grown the structure by 4 bytes. If you put it between
current_cmnd and queue_depth, you won't grow the struct at all.
next prev parent reply other threads:[~2006-03-30 16:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 23:55 Compaq Fiber Channel Array RM4000 / Scsi middle ware driver Ingo Flaschberger
2006-02-28 0:23 ` Ingo Flaschberger
2006-02-28 0:32 ` Ingo Flaschberger
2006-02-28 0:40 ` Matthew Wilcox
2006-03-22 18:17 ` Ingo Flaschberger
2006-03-22 18:41 ` Martin K. Petersen
2006-03-22 19:58 ` Ingo Flaschberger
2006-03-22 20:02 ` Matthew Wilcox
2006-03-22 20:13 ` Ingo Flaschberger
2006-03-28 19:43 ` Compaq Fiber Channel Array RM4000 / SCSI Problems / Need HELP! Ingo Flaschberger
2006-03-29 6:07 ` Martin K. Petersen
2006-03-29 11:17 ` Ingo Flaschberger
2006-03-29 13:10 ` Compaq Fiber Channel Array RM4000 / Kernel implementation Ingo Flaschberger
2006-03-29 13:19 ` typo in scsi_devinfo.h Ingo Flaschberger
2006-03-29 13:43 ` Matthew Wilcox
2006-03-29 15:07 ` Compaq Fiber Channel Array RM4000 / Kernel implementation Christoph Hellwig
2006-03-29 16:47 ` Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch Ingo Flaschberger
2006-03-29 17:29 ` James Bottomley
2006-03-29 17:53 ` Ingo Flaschberger
2006-03-29 18:22 ` James Bottomley
2006-03-29 18:35 ` Ingo Flaschberger
2006-03-29 18:43 ` James Bottomley
2006-03-29 18:54 ` Ingo Flaschberger
2006-03-29 19:03 ` James Bottomley
2006-03-29 20:23 ` Ingo Flaschberger
2006-03-29 21:11 ` James Bottomley
2006-03-30 10:53 ` Ingo Flaschberger
2006-03-30 12:58 ` Matthew Wilcox
2006-03-30 14:20 ` Ingo Flaschberger
2006-03-30 14:46 ` James Bottomley
2006-03-30 15:04 ` Ingo Flaschberger
2006-03-30 15:09 ` James Bottomley
2006-03-30 15:54 ` Ingo Flaschberger
2006-03-30 16:13 ` Patrick Mansfield
2006-03-30 16:25 ` Ingo Flaschberger
2006-03-30 16:24 ` Matthew Wilcox [this message]
2006-03-30 16:35 ` Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch VER6 Ingo Flaschberger
2006-03-31 17:36 ` Ingo Flaschberger
2006-03-31 19:45 ` James Bottomley
2006-03-31 21:13 ` Ingo Flaschberger
2006-03-31 21:21 ` James Bottomley
2006-03-31 21:24 ` Ingo Flaschberger
2006-04-01 1:16 ` Ingo Flaschberger
2006-04-01 2:07 ` James Bottomley
2006-04-01 16:46 ` Ingo Flaschberger
2006-04-06 11:21 ` Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch VER7 Ingo Flaschberger
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=20060330162429.GI13590@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=if@xip.at \
--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;
as well as URLs for NNTP newsgroup(s).