From: Matthew Wilcox <willy@debian.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
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: Mon, 6 Sep 2004 02:58:36 +0100 [thread overview]
Message-ID: <20040906015836.GX642@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1094306082.1924.0.camel@mulgrave>
On Sat, Sep 04, 2004 at 09:54:40AM -0400, James Bottomley wrote:
> On Sat, 2004-09-04 at 00:48, Mike Christie wrote:
> > device_add calls kobject_add which can sleep.
>
> Yes, I'll move it outside the lock.
>
> I suppose I should add a comment somewhere about our critical dependence
> on sequential LUN scanning as well just in case someone tries to
> parallelise it.
sequential on a given bus, rather than globally, right? There's no
problem with scanning different busses simultanously, is there?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-09-06 1:58 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 [this message]
2004-09-06 2:05 ` James Bottomley
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=20040906015836.GX642@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mikenc@us.ibm.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