thanks, applied.
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Jack Morgenstein wrote:
I have not yet submitted the patch to the list.
sounds like its about time to do that... could you send this to
review/merge into 2.6.37?
From what was commented here and further looking, the sentence [...]
Upon receiving this trap, OpenSM initiates a heavy sweep,
The Node Description cannot be changed via MADs (it is read-only).
Until now, it was changed in the driver via sysfs, and the new Node
Description was simply inserted by the driver into MAD responses
(replacing the description returned by FW).
Until now, openibd used the sysfs interface to change
of the openibd
service a trap will be sent to opensm and the latter will heavy sweep?! this
doesn't sound very much scalable...
have you tested it over large clusters? what was the impact?
Or.
mlx4: propagate node_description changes down to FW.
The Node Description cannot be changed via MADs
: Sunday, October 03, 2010 5:31 PM
To: Jack Morgenstein; linux-rdma
Subject: re: mlx4: propagate node_description changes down to FW
Hi Jack,
I just came across this patch of yours which was placed in ofed 1.5.2, I didn't
see any track of it
here @ linux-rdma (any specific reason
]
Sent: Sunday, October 03, 2010 5:31 PM
To: Jack Morgenstein; linux-rdma
Subject: re: mlx4: propagate node_description changes down to FW
Hi Jack,
I just came across this patch of yours which was placed in ofed 1.5.2, I
didn't see any track of it
here @ linux-rdma (any specific reason
