From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Mike Christie <mikenc@us.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] exposing the sdev_target in sysfs
Date: 05 Sep 2004 22:05:42 -0400 [thread overview]
Message-ID: <1094436343.10976.29.camel@mulgrave> (raw)
In-Reply-To: <20040906015836.GX642@parcelfarce.linux.theplanet.co.uk>
On Sun, 2004-09-05 at 21:58, Matthew Wilcox wrote:
> sequential on a given bus, rather than globally, right? There's no
> problem with scanning different busses simultanously, is there?
Actually, no, sequential within a given target. Ensuring this
sequentiality is entirely the province of the scsi subsystem, so as long
as we do the right thing it doesn't matter how parallel we make the bus
scans.
James
next prev parent reply other threads:[~2004-09-06 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 23:40 [RFC] exposing the sdev_target in sysfs James Bottomley
2004-09-04 4:48 ` Mike Christie
2004-09-04 13:54 ` James Bottomley
2004-09-06 1:58 ` Matthew Wilcox
2004-09-06 2:05 ` James Bottomley [this message]
2004-09-04 7:24 ` Olaf Hering
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=1094436343.10976.29.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mikenc@us.ibm.com \
--cc=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox