linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: RFC: InfiniBand hotplug agent
Date: Thu, 23 Mar 2006 17:11:02 +0000	[thread overview]
Message-ID: <adapskdw0gp.fsf@cisco.com> (raw)
In-Reply-To: <ada1wwu47xf.fsf@cisco.com>

    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".

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?

Thanks,
  Roland


-------------------------------------------------------
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

  parent reply	other threads:[~2006-03-23 17:11 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 [this message]
2006-03-23 23:31 ` Greg KH

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=adapskdw0gp.fsf@cisco.com \
    --to=rdreier@cisco.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).