public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Morgenstein <jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Mike Heinz <michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH v2] ofa_kernel/infiniband node description patch
Date: Wed, 16 Jun 2010 15:38:08 +0300	[thread overview]
Message-ID: <201006161538.09029.jackm@dev.mellanox.co.il> (raw)
In-Reply-To: <4C2744E8AD2982428C5BFE523DF8CDCB49D09E7A00-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>

On Tuesday 15 June 2010 23:20, Mike Heinz wrote:
> Well, the feedback from you was about making sure the description was null terminated.
Actually, that feedback was from me :).

> This *is* settable through sysfs, and still is even when the patch is applied. The problem is that the current model is to set the description once, at boot time, through an init script. This will often cause the description to be set incorrectly, because the host name has not been set at the time the script is run.
> 
> The reason I changed the default behavior for the various HCAs was because it simply seems like a smarter default behavior than simply setting it to the model of the HCA.
> 
> So, basically, if you have an init script to set the node descriptions it will still work - but this patch makes it unlikely you will need such a script in the first place.
> 
Actually, you will still need the install-script setting.  If you have several HCA's of the same type installed on a single host,
they will all get the same node description.
If you wish to differentiate between the different HCA's (which openibd does), you will still need the install script.

Finally, I'm not convinced that changing the default behavior (to have utsname: <fw burned description>) is necessary.
I think it is redundant, since the sysfs-interface is always available (which can make use of the "@" improvement).  

-Jack
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-06-16 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 19:35 [PATCH v2] ofa_kernel/infiniband node description patch Mike Heinz
     [not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB49D09E79E8-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-06-15 20:10   ` Jason Gunthorpe
     [not found]     ` <20100615201000.GD4630-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-06-15 20:20       ` Mike Heinz
     [not found]         ` <4C2744E8AD2982428C5BFE523DF8CDCB49D09E7A00-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-06-16 12:38           ` Jack Morgenstein [this message]
     [not found]             ` <201006161538.09029.jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-06-16 13:53               ` Mike Heinz

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=201006161538.09029.jackm@dev.mellanox.co.il \
    --to=jackm-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
    --cc=ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.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