public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
To: Mike Heinz <michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: Jack Morgenstein <jackm-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
	linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ewg] [PATCH] node description patch
Date: Mon, 14 Jun 2010 10:43:06 +0300	[thread overview]
Message-ID: <4C15DD8A.3010806@Voltaire.com> (raw)
In-Reply-To: <4C2744E8AD2982428C5BFE523DF8CDCB49A488D73B-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>

Mike Heinz wrote:
> This patch fixes a problem with the openibd initialization script. 
> On machines using slower DHCP servers, openibd frequently sets the HCA's node description 
> to HCA-1. This patch modifies openibd to add a "@" instead of the hostname and adds a 
> small hook in the core drivers to replace the "@" sign with the system's utsname().
> Because this patch depends on changes to openibd, it cannot be submitted 
> to the upstream kernel, but it still corrects an outstanding issue with OFED 

Mike, 

The fact that you patch is both to user and kernel space code doesn't mean the kernel part can't be submitted upstream. I suggested you re post the patches to linux-rdma in a series made of two patches, one to the kernel and one to the service script. The kernel part then could be picked by the maintainer and will come into play once there's user space code plugging to it. This is similar to cases where people have kernel netlink agent code, merging is not dependent on the existence of specific matching user space code.

As for the user space part, the IB stack provided by the distros does have a service script and this service script attempts to set the node descriptor, e.g here's the RHEL6 beta rdma service code 

> # grep -A 13 "node description" /etc/rc.d/init.d/rdma
>     # Add node description to sysfs
>     IBSYSDIR="/sys/class/infiniband"
>     if [ -d ${IBSYSDIR} ]; then
>         declare -i hca_id=1
>         for hca in ${IBSYSDIR}/*
>         do
>             if [ -w ${hca}/node_desc ]; then
>                 echo -n "$(hostname | cut -f 1 -d .) HCA-${hca_id}" >> ${hca}/node_desc 2> /dev/null
>             fi
>             let hca_id++
>         done
>     fi
> 
>     errata_58

If you want to patch this, you can here open a bugzilla case with the relevant distro and propose a patch.

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

       reply	other threads:[~2010-06-14  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C2744E8AD2982428C5BFE523DF8CDCB49A488D73B@MNEXMB1.qlogic.org>
     [not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB49A488D73B-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-06-14  7:43   ` Or Gerlitz [this message]
     [not found]     ` <4C15DD8A.3010806-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-06-14 13:05       ` [ewg] [PATCH] node description patch 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=4C15DD8A.3010806@Voltaire.com \
    --to=ogerlitz-hkgkho2ms0fwk0htik3j/w@public.gmane.org \
    --cc=jackm-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@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