From: Linas Vepstas <linas@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplugging ethernet cables.
Date: Tue, 04 Jan 2005 17:44:18 +0000 [thread overview]
Message-ID: <20050104174418.GN3333@austin.ibm.com> (raw)
In-Reply-To: <41D74A49.2060607@are-b.org>
Hi,
A naive question re ethernet hotplug: what if its iSCSI?
On Sun, Jan 02, 2005 at 01:43:32AM +0100, Kay Sievers was heard to remark:
> On Sun, 2005-01-02 at 02:11 +0100, oliver wrote:
> > They mention ifplugd and even though this seems to work reasonably, I
> > was wondering why hotplugging doesn't support ethernet hotplugging
> > nativly?
>
> Hotplug supports device add and remove, not state changes of hardware.
>
> > As I understand it the hotplugging daemon responds to events
> > created by several devices, where the ifplugd polls and the device.
>
> There is no such daemon involved in the hotplug handling. Hotplug is
> driven by more or less stateless scripts invoked by the kernel.
>
> The network link state changes can be received on a netlink socket from
> the kernel. These events are not hotplug events and don't really fit
> into the model of linux hotplug.
I can imagine a scenario where Linux has mounted a filesystem that
is sitting on an iSCSI disk device. Thus, in many respects, this is
analogous to a USB disk being plugged and unplugged. I also presume
that iSCSI devices need not be just disks, but could be "anything",
thus making the situation even more analogous to USB.
I'm also curious about plans for things like infiniband fabrics,
which might be plugged/unplugged in various ways, which the OS might
want to know about. Again, this seems clearly analogous to USB fabrics
...
--linas
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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
next prev parent reply other threads:[~2005-01-04 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 0:12 Hotplugging ethernet cables oliver
2005-01-02 0:43 ` Kay Sievers
2005-01-04 17:44 ` Linas Vepstas [this message]
2005-01-04 18:38 ` Kay Sievers
2005-01-05 11:29 ` Oliver Schinagl
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=20050104174418.GN3333@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).