From: Arjan van de Ven <arjanv@redhat.com>
To: "Surekha.PC" <surekhap@cisco.com>
Cc: 'SCSI Mailing List' <linux-scsi@vger.kernel.org>
Subject: Re: iSCSI device naming issues
Date: Sun, 04 Jul 2004 21:57:44 +0200 [thread overview]
Message-ID: <1088971063.2736.10.camel@laptop.fenrus.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAANoIxZIFzbEaqwjJgytz2AeKAAAAQAAAAXdSfMOoTnU6X86O4sbqWzAEAAAAA@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
On Thu, 2004-07-01 at 15:58, Surekha.PC wrote:
> Whenever an iSCSI device is configured in the system, a hotplug
> event is generated which invokes udev for device node creation.
> iSCSI driver has a CALLOUT rule for udev to generate a unique
> name for iSCSI devices.
wouldn't this all be a lot cleaner if you follow the
one-hba-per-remote-host model ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-04 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 13:58 iSCSI device naming issues Surekha.PC
2004-07-01 15:57 ` Mike Anderson
2004-07-01 17:29 ` udev naming of st devices [was Re: iSCSI device naming issues] Patrick Mansfield
2004-07-04 19:57 ` Arjan van de Ven [this message]
2004-07-07 9:05 ` iSCSI device naming issues Surekha.PC
2004-07-04 20:11 ` Christoph Hellwig
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=1088971063.2736.10.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=surekhap@cisco.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