From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Asynchronous scsi scanning Date: Tue, 15 May 2007 06:02:28 -0600 Message-ID: <20070515120228.GI10562@parisc-linux.org> References: <20070513160608.GA29024@redhat.com> <1179072655.3723.42.camel@mulgrave.il.steeleye.com> <1179073116.3723.45.camel@mulgrave.il.steeleye.com> <1179153096.3703.23.camel@mulgrave.il.steeleye.com> <17841.simon.1179228389@5ec7c279.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:41827 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755887AbXEOMCe (ORCPT ); Tue, 15 May 2007 08:02:34 -0400 Content-Disposition: inline In-Reply-To: <17841.simon.1179228389@5ec7c279.invalid> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Simon Arlott Cc: James Bottomley , Dave Jones , Linux Kernel Mailing List , linux-scsi@vger.kernel.org, kernel-packagers@vger.kernel.org On Tue, May 15, 2007 at 12:26:29PM +0100, Simon Arlott wrote: > I've already suggested a sysfs attribute - or something equivalent - would > be much better. It's just one function that a user might want to run multiple > times (e.g. after adding scsi devices?) - why should loading a module be used > for this? It's easy to suggest a sysfs attribute. What you've failed to do is suggest the pathname of the sysfs attribute, the contents of it, or the semantics of it (read-only? read-write? write-only? blocking?) My personal favourite would be to add a new verb to /proc/scsi/scsi, but James dislikes that idea. I'd *really* like to hear from distro people. What is the most convenient way for you to implement "load all the scsi modules, then wait until all devices are found"? James and I had thought that loading a new module would be the easiest way for you, but it seems inconvenient for you.