Jack,
The way we handle that right now is in the openibd start script. What we do is
this:
ib_set_node_desc()
{
# Add node description to sysfs
ibsysdir="/sys/class/infiniband"
if [ -d ${ibsysdir} ]; then
declare -i hca_id=1
for hca in ${ibsysdir}/*
do
if [ -e ${hca}/node_desc ]; then
logger -i "Set node_desc for $(basename $hca)"
echo -n "@ HCA-${hca_id}" >> ${hca}/node_desc
fi
let hca_id++
done
fi
}
Once the kernel modification is accepted, I plan to submit a patch for the
openibd script.
-----Original Message-----
From: Jack Morgenstein [mailto:[email protected]]
Sent: Saturday, February 19, 2011 2:23 AM
To: Roland Dreier
Cc: Mike Heinz; [email protected]; Hal Rosenstock
Subject: Re: [PATCH 0/2] Improved node descriptions
On Friday 18 February 2011 01:20, Roland Dreier wrote:
> This looks like a reasonable approach to me, although of course the SM
> has no way of knowing it should update a port's node description if a
> hostname changes.
>
What about the problem of multiple HCA's of the same type on a single host?
Won't all of them get the identical node description?
Mike, can you add something to handle this case?
(See my original feedback:
http://www.mail-archive.com/[email protected]/msg04413.html
and see Mike's response:
http://www.mail-archive.com/[email protected]/msg04414.html
Mike, I agree that doing something for the upstream is better than doing
nothing, but I would still like to see the multiple-HCA case handled. I think
this can be done by adding a query to the low-level driver to distinguish
between
HCAs).
-Jack
This message and any attached documents contain information from QLogic
Corporation or its wholly-owned subsidiaries that may be confidential. If you
are not the intended recipient, you may not read, copy, distribute, or use this
information. If you have received this transmission in error, please notify the
sender immediately by reply e-mail and then delete this message.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
