From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: RFC: InfiniBand hotplug agent
Date: Thu, 23 Mar 2006 23:31:05 +0000 [thread overview]
Message-ID: <20060323233105.GB31490@kroah.com> (raw)
In-Reply-To: <ada1wwu47xf.fsf@cisco.com>
On Thu, Mar 23, 2006 at 09:11:02AM -0800, Roland Dreier wrote:
> Greg> Why does your drivers care about the hostname? The kernel
> Greg> already knows this information anyway...
>
> As I explained before, this script puts the hostname in the InfiniBand
> "node description," which is retrieved by various IB network
> management tools. It makes the output of these tools much easier to
> read, since you can see things like "node1 (CA)" and "node2 (CA)" in
> the network management tools instead of just two copies of "CA".
Ick, the kernel is then printing that data back out somewhere else? I
really don't want to know... :)
> Yes, I could modify the driver to look at system_utsname and pick a
> way to format that. But that suffers from the problem of putting
> policy in the kernel (who picks the format for node descriptions?),
> although that's minor. And we still have the problem of what to do
> before the hostname is set -- put "(none)" in our node description?
>
> Anyway, do you think just having this node description setting in the
> kernel is the best way to go?
I think that your proposed solution will not work on the current round
of "enterprise" distros, so I don't think it is a real "solution".
As for a proposed one, I have no idea, sorry.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&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
prev parent reply other threads:[~2006-03-23 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 19:05 RFC: InfiniBand hotplug agent Roland Dreier
2006-03-22 19:47 ` Marco d'Itri
2006-03-22 20:36 ` Roland Dreier
2006-03-23 5:13 ` Greg KH
2006-03-23 15:19 ` Scott James Remnant
2006-03-23 17:11 ` Roland Dreier
2006-03-23 23:31 ` Greg KH [this message]
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=20060323233105.GB31490@kroah.com \
--to=greg@kroah.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 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.