> -----Original Message-----
> From: [email protected] [mailto:linux-rdma-
> Subject: Re: Node Description mismatch between saquery & smpquery
> 
> On Tue, 2013-06-18 at 07:13 -0400, Hal Rosenstock wrote:
> > On 6/17/2013 5:38 PM, Albert Chu wrote:
> > > We've recently noticed that the Node Description for a node can
> > > mis-mismatch between the output of smpquery and saquery.  For
> example:
> > >
> > > # smpquery NodeDesc 427
> > > Node Description:.................sierra1932 qib0
> > >
> > > # saquery NodeRecord 427 | grep NodeDesc
> > >                 NodeDescription.........QLogic Infiniband HCA
> > >
> > > A restart of OpenSM is the current solution to resolve this.

[snip]

> > >
> > > When the node descriptor is changed, a trap should be sent to opensm
> > > indicating the change.  Normally OpenSM gets the trap and reads the
> > > new node descriptor.
> >
> > Are you sure the trap is being issued by those devices when the
> > NodeDescription is changed locally ?
> 
> These particular devices do support the trap and tests show they do send
> traps on changes (i.e. manually changing
> /sys/class/infiniband/qib0/node_desc).
> 
> > Also, if so, do these devices implement timeout/retry on sending the
> > trap (e.g. trying to make sure that they receive trap repress before
> > giving up on trap) ?
> 
> This I don't know.  I've been trying to figure out if they do and if they do 
> how
> it might be configurable.  Is there a way to figure this out?
> 

Looking quickly at the driver I don't think it does resend the trap.  However, 
Mike might know better: CC'ed.

Ira

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

Reply via email to