All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Hannes Reinecke <hare@suse.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: 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: Fri, 18 Mar 2016 14:56:10 -0700	[thread overview]
Message-ID: <56EC797A.8000104@sandisk.com> (raw)
In-Reply-To: <1458200385-32088-1-git-send-email-hare@suse.de>

On 03/17/2016 12:39 AM, 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.

Hello Hannes,

Will setting scsi_scan_type to 'manual' allow a system to boot from a 
SCSI disk? If not, are there alternatives to this approach? Would it be 
a valid alternative to e.g. introduce a new threshold parameter such 
that only LUN numbers below this threshold are scanned during boot?

Thanks,

Bart.

  parent reply	other threads:[~2016-03-18 21:56 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 [this message]
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

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=56EC797A.8000104@sandisk.com \
    --to=bart.vanassche@sandisk.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 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.