From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linas Vepstas <linas@austin.ibm.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-hotplug-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Alexander E. Patrakov" <patrakov@ums.usu.ru>,
linux-scsi@vger.kernel.org,
Patrick Mansfield <patmans@us.ibm.com>
Subject: Re: Asynchronous scsi scanning, version 9
Date: Wed, 28 Jun 2006 07:52:27 +0000 [thread overview]
Message-ID: <44A2353B.1080105@suse.de> (raw)
In-Reply-To: <1151356477.2673.41.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-06-26 at 15:58 -0500, Linas Vepstas wrote:
>> I guess there's no way of figuring out where the root disk is, and
>> waiting only for that?
>
> Well, sure, but you'd do that at user level: you know what the root
> disk is, so you just wait on the udev event announcing its arrival.
>
Exactly. And it works well.
The only point left addressing is that you never know how long you
should be waiting. It would be nice if the transport class / SCSI ML
could give some hint somewhere to the effect 'scanning in progress'.
Otherwise you'll end up using arbitrary timeouts and you'll always find
machines where this timeout doesn't work :-(
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux Products GmbH S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
WARNING: multiple messages have this Message-ID (diff)
From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linas Vepstas <linas@austin.ibm.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-hotplug-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Alexander E. Patrakov" <patrakov@ums.usu.ru>,
linux-scsi@vger.kernel.org,
Patrick Mansfield <patmans@us.ibm.com>
Subject: Re: Asynchronous scsi scanning, version 9
Date: Wed, 28 Jun 2006 09:52:27 +0200 [thread overview]
Message-ID: <44A2353B.1080105@suse.de> (raw)
In-Reply-To: <1151356477.2673.41.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-06-26 at 15:58 -0500, Linas Vepstas wrote:
>> I guess there's no way of figuring out where the root disk is, and
>> waiting only for that?
>
> Well, sure, but you'd do that at user level: you know what the root
> disk is, so you just wait on the udev event announcing its arrival.
>
Exactly. And it works well.
The only point left addressing is that you never know how long you
should be waiting. It would be nice if the transport class / SCSI ML
could give some hint somewhere to the effect 'scanning in progress'.
Otherwise you'll end up using arbitrary timeouts and you'll always find
machines where this timeout doesn't work :-(
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux Products GmbH S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-
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
next prev parent reply other threads:[~2006-06-28 7:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 14:33 [RFC] Asynchronous scsi scanning Matthew Wilcox
2006-05-11 18:15 ` Mike Christie
2006-05-11 18:21 ` Matthew Wilcox
2006-05-11 18:49 ` Mike Christie
2006-05-11 18:56 ` Matthew Wilcox
2006-05-11 19:09 ` Mike Christie
2006-05-18 17:22 ` [PATCH] " Matthew Wilcox
2006-05-29 3:19 ` Asynchronous scsi scanning, version 9 Matthew Wilcox
2006-05-29 8:38 ` Stefan Richter
2006-05-29 13:05 ` Matthew Wilcox
2006-05-29 13:11 ` Arjan van de Ven
2006-05-29 13:19 ` Matthew Wilcox
2006-05-31 23:21 ` Patrick Mansfield
2006-05-31 23:21 ` Patrick Mansfield
2006-06-01 12:22 ` Kay Sievers
2006-06-01 12:22 ` Kay Sievers
2006-10-26 19:53 ` maximilian attems
2006-10-26 19:53 ` maximilian attems
2006-06-01 13:14 ` Alexander E. Patrakov
2006-06-01 13:14 ` Alexander E. Patrakov
2006-06-01 13:21 ` maximilian attems
2006-06-01 13:21 ` maximilian attems
2006-06-01 13:23 ` Matthew Wilcox
2006-06-01 13:23 ` Matthew Wilcox
2006-06-01 13:26 ` Alexander E. Patrakov
2006-06-01 13:26 ` Alexander E. Patrakov
2006-06-01 14:00 ` Arjan van de Ven
2006-06-01 14:00 ` Arjan van de Ven
2006-06-25 21:15 ` James Bottomley
2006-06-25 21:15 ` James Bottomley
2006-06-25 22:46 ` Matthew Wilcox
2006-06-25 22:46 ` Matthew Wilcox
2006-06-26 8:24 ` Arjan van de Ven
2006-06-26 8:24 ` Arjan van de Ven
2006-06-26 12:40 ` Matthew Wilcox
2006-06-26 12:40 ` Matthew Wilcox
2006-06-26 12:59 ` Arjan van de Ven
2006-06-26 12:59 ` Arjan van de Ven
2006-06-26 16:03 ` Greg KH
2006-06-26 16:03 ` Greg KH
2006-06-26 14:44 ` Matthew Dharm
2006-06-26 14:44 ` Matthew Dharm
2006-06-26 15:18 ` Matthew Wilcox
2006-06-26 15:18 ` Matthew Wilcox
2006-06-26 15:44 ` James Bottomley
2006-06-26 15:44 ` James Bottomley
2006-06-26 16:02 ` Greg KH
2006-06-26 16:02 ` Greg KH
2006-06-26 21:08 ` Matthew Dharm
2006-06-26 21:08 ` Matthew Dharm
2006-06-26 22:15 ` Matthew Wilcox
2006-06-26 22:15 ` Matthew Wilcox
2006-06-26 18:55 ` [SPAM] " Doug Ledford
2006-06-26 18:55 ` Doug Ledford
2006-06-26 21:04 ` Matthew Dharm
2006-06-26 21:04 ` Matthew Dharm
2006-06-26 21:20 ` Doug Ledford
2006-06-26 21:20 ` Doug Ledford
2006-06-26 20:58 ` Linas Vepstas
2006-06-26 20:58 ` Linas Vepstas
2006-06-26 21:14 ` James Bottomley
2006-06-26 21:14 ` James Bottomley
2006-06-26 21:21 ` Linas Vepstas
2006-06-26 21:21 ` Linas Vepstas
2006-06-26 21:41 ` James Bottomley
2006-06-26 21:41 ` James Bottomley
2006-06-28 7:52 ` Hannes Reinecke [this message]
2006-06-28 7:52 ` Hannes Reinecke
2006-06-28 16:03 ` James Bottomley
2006-06-28 16:03 ` James Bottomley
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=44A2353B.1080105@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=linas@austin.ibm.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=patmans@us.ibm.com \
--cc=patrakov@ums.usu.ru \
--cc=stefanr@s5r6.in-berlin.de \
/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.