All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: PATCH 2/5: scsi-scan-blist_replun
Date: Wed, 21 Apr 2004 17:30:30 +0200	[thread overview]
Message-ID: <20040421153030.GE29699@tpkurt.garloff.de> (raw)
In-Reply-To: <20040421161412.B6793@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]

Hi Christoph,

On Wed, Apr 21, 2004 at 04:14:12PM +0100, Christoph Hellwig wrote:
> Hmm, where does this number come from?

1 page. I've mentioned it in the email.

> >  	/*
> > -	 * Only support SCSI-3 and up devices.
> > -	 */
> > -	if (sdev->scsi_level < SCSI_3)
> > +	 * Only support SCSI-3 and up devices if BLIST_NOREPORTLUN is not set.
> > +	 * Also allow SCSI-2 if BLIST_REPORTLUN2 is set and host adapter does
> > +	 * support more than 8 LUNs.
> 
> This comment and the nested if is a little confusing.  Also why shouldn't
> the arbitrary SCSI2 limit for BLIST_REPORTLUN2?  I'm sure we won't find
> SCSI1 devices supporting it, but there should not be any harm leaving out
> that check - and doing so makes the logic much cleaner.

It's just straightforward plain simple boolean logic ;-)

I think default_dev_flags=0x20000 would be a good default for many
machines out there, so don't take a risk of breaking SCSI-1 devices.
That's why the check for a HBA which support more than 8 LUNs is in
there as well.

> 	/*
> 	 * REPORT_LUN is used by default only for SCSI 3 devices (unless
> 	 * BLIST_NOREPORTLUN is set).  For other devices BLIST_REPORTLUN
> 	 * enables it if the HBA does support more than 8 LUNs.
> 
> 	 if (bflags & BLIST_NOREPORTLUN)
> 	 	return 1;
> 	 if (sdev->scsi_level < 3 && sdev->host->max_lun <= 8 &&
> 	     !(bflags & BLIST_REPORTLUN2))
> 	     	return 1;
> 
> Note that I'd prefer not to add BLIST_NOREPORTLUN if the discussing
> about the LUN mapping comes to a useable consensus.

I'm sure there will be devices that are SCSI-3 and break on REPORT_LUNS.
It's not just for helping those devs that don't fit into our 32bit LUN
scheme. Also we need to have a replacement for the CONFIG option that
used to be there before.

Regards,
-- 
Kurt Garloff                   <kurt@garloff.de>             [Koeln, DE]
Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL]
Linux: SUSE Labs (Head)        <garloff@suse.de>    [SUSE Nuernberg, DE]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-21 15:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-18 18:57 Patches for SCSI scanning Kurt Garloff
2004-04-18 23:16 ` James Bottomley
2004-04-20 11:54   ` Kurt Garloff
2004-04-20 12:04     ` Christoph Hellwig
2004-04-20 13:02       ` Kurt Garloff
2004-04-20 14:38     ` James Bottomley
2004-04-20 16:03       ` Kurt Garloff
2004-04-20 16:08         ` James Bottomley
2004-04-21 13:48           ` Kurt Garloff
2004-04-21 15:36             ` James Bottomley
2004-04-21 13:45         ` Kurt Garloff
2004-04-21 14:10           ` PATCH 1/5: scsi-scan-deprecate-forcelun Kurt Garloff
2004-04-21 14:12           ` PATCH 2/5: scsi-scan-blist_replun Kurt Garloff
2004-04-21 15:14             ` Christoph Hellwig
2004-04-21 15:30               ` Kurt Garloff [this message]
2004-04-21 16:03               ` Kurt Garloff
2004-04-21 14:13           ` PATCH 3/5: scsi-scan-no-offl-pq-notcon Kurt Garloff
2004-04-21 14:14           ` PATCH 4/5: scsi-scan-dont-att-pq-notcon Kurt Garloff
2004-04-21 15:02             ` Christoph Hellwig
2004-04-21 15:24               ` Kurt Garloff
2004-04-21 15:33                 ` Mike Anderson
2004-04-21 15:33                 ` Christoph Hellwig
2004-04-21 16:08                   ` Kurt Garloff
2004-04-21 16:18                     ` James Bottomley
2004-04-21 16:55                       ` Patrick Mansfield
2004-04-21 22:51                         ` Kurt Garloff
2004-04-22 20:39                           ` Patrick Mansfield
2004-04-22 20:45                             ` James Bottomley
2004-04-21 16:58                       ` Kurt Garloff
2004-04-21 16:16                   ` Kurt Garloff
2004-04-21 15:40             ` James Bottomley
2004-04-21 14:14           ` PATCH 5/5: scsi-scan-inq-timeout Kurt Garloff
2004-04-21 20:24             ` Patrick Mansfield
2004-04-21 22:48               ` Kurt Garloff
2004-04-21 23:49                 ` Patrick Mansfield
2004-04-20 16:26       ` Patches for SCSI scanning Patrick Mansfield
2004-04-20 16:42         ` Kurt Garloff
2004-04-20 17:44           ` Patrick Mansfield
2004-04-21 13:52             ` Kurt Garloff
2004-04-20 10:24 ` Fabien Salvi

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=20040421153030.GE29699@tpkurt.garloff.de \
    --to=garloff@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.