From: Benjamin Block <bblock@linux.vnet.ibm.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCHv3] scsi: disable automatic target scan
Date: Tue, 5 Apr 2016 14:20:46 +0200 [thread overview]
Message-ID: <20160405122046.GC13317@bblock-ThinkPad-W530> (raw)
In-Reply-To: <56FE234B.8090904@suse.de>
On 09:29 Fri 01 Apr , Hannes Reinecke wrote:
> On 03/30/2016 09:41 PM, Benjamin Block wrote:
> > Hello Hannes,
> >
> > I am a bit late here, but as this got pulled and Steffen didn't have
> > time to give it a review, I did today.
> >
> > On 08:39 Thu 17 Mar , Hannes Reinecke wrote:
> >> On larger installations it is useful to disable automatic LUN
> >> scanning, and only add the required LUNs via udev rules.
> >> This can speed up bootup dramatically.
> >>
> >> This patch introduces a new scan module parameter value 'manual',
> >> which works like 'none', but can be overriden by setting the 'rescan'
> >> value from scsi_scan_target to 'SCSI_SCAN_MANUAL'.
> >> And it updates all relevant callers to set the 'rescan' value
> >> to 'SCSI_SCAN_MANUAL' if invoked via the 'scan' option in sysfs.
> >>
> >> Signed-off-by: Hannes Reinecke <hare@suse.de>
> >> ---
> >
> > [:snip:]
> >
> >>
> >> diff --git a/drivers/s390/scsi/zfcp_unit.c b/drivers/s390/scsi/zfcp_unit.c
> >> index 157d3d2..08bba7c 100644
> >> --- a/drivers/s390/scsi/zfcp_unit.c
> >> +++ b/drivers/s390/scsi/zfcp_unit.c
> >> @@ -26,7 +26,8 @@ void zfcp_unit_scsi_scan(struct zfcp_unit *unit)
> >> lun = scsilun_to_int((struct scsi_lun *) &unit->fcp_lun);
> >>
> >> if (rport && rport->port_state == FC_PORTSTATE_ONLINE)
> >> - scsi_scan_target(&rport->dev, 0, rport->scsi_target_id, lun, 1);
> >> + scsi_scan_target(&rport->dev, 0, rport->scsi_target_id, lun,
> >> + SCSI_SCAN_RESCAN);
> >
> > I'd rather use the new SCSI_SCAN_MANUAL here. We don't want this to be
> > "blocked" by an attribute set in a different (new) code-path and
> > config-location.
> >
> > This path is used by both, zfcp-recovery and -userinterfaces (sysfs) and
> > in both cases we call it with the intend that the scan is really done -
> > hence the SCSI_SCAN_MANUAL to force a scan. I'd find it very weird if
> > suddenly our users would have to additionally use yet an other config to
> > get the old interfaces working properly.
> >
> Okay, no problem with that.
> zfcp has its own scanning rules (cf allow_lun_scan module parameter), so
> setting it to 'MANUAL' will just restore the original behaviour.
>
> Will you be sending a patch for it?
>
Yeah, sry, once I am through our backlog and I find time to test that
properly.
Beste Grüße / Best regards,
- Benjamin Block
--
Linux on z Systems Development / IBM Systems & Technology Group
IBM Deutschland Research & Development GmbH
Vorsitz. AufsR.: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: AmtsG Stuttgart, HRB 243294
--
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
prev parent reply other threads:[~2016-04-05 12:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 7:39 [PATCHv3] scsi: disable automatic target scan Hannes Reinecke
2016-03-18 19:39 ` Ewan D. Milne
2016-03-18 21:56 ` Bart Van Assche
2016-03-19 15:18 ` Hannes Reinecke
2016-03-19 15:29 ` Laurence Oberman
2016-03-21 1:24 ` Bart Van Assche
2016-03-21 7:15 ` Hannes Reinecke
2016-03-21 20:40 ` Laurence Oberman
2016-03-22 17:36 ` Hannes Reinecke
2016-03-24 2:35 ` Laurence Oberman
2016-03-29 0:27 ` Martin K. Petersen
2016-03-30 19:41 ` Benjamin Block
2016-04-01 7:29 ` Hannes Reinecke
2016-04-05 12:20 ` Benjamin Block [this message]
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=20160405122046.GC13317@bblock-ThinkPad-W530 \
--to=bblock@linux.vnet.ibm.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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