Re: [PATCH] infiniband-diags: Add SMP/QP0 usage explanation to general man page

[Hal Rosenstock <hal@xxxxxxxxxxxxxxxxxx>]

On 5/31/2012 7:58 PM, Ira Weiny wrote:
> On Thu, 31 May 2012 19:35:32 -0400
> Hal Rosenstock <hal@xxxxxxxxxxxxxxxxxx> wrote:
> 
>> On 5/31/2012 7:02 PM, Ira Weiny wrote:
>>>
>>>
>>> Signed-off-by: Ira Weiny <weiny2@xxxxxxxx>
>>> ---
>>>  doc/rst/infiniband-diags.8.in.rst |   12 ++++++++++++
>>>  1 files changed, 12 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/doc/rst/infiniband-diags.8.in.rst b/doc/rst/infiniband-diags.8.in.rst
>>> index 6a86ae2..9cd4524 100644
>>> --- a/doc/rst/infiniband-diags.8.in.rst
>>> +++ b/doc/rst/infiniband-diags.8.in.rst
>>> @@ -23,6 +23,18 @@ may therefore work even in unconfigured subnets.  Other, higher level
>>>  utilities, require LID routed MAD's and to some extent SA/SM access.
>>>  
>>>  
>>> +THE USE OF SMP's (QP0)
>>> +======================
>>> +
>>> +Many of the tools in this package rely on the use of SMP's via QP0 to acquire
>>
>> SMPs
> 
> done
> 
>>
>>> +data directly from hardware.  
>>
>> SMA rather than hardware
> 
> done.
> 
>>
>>> While this mode of operation is not technically
>>> +in compliance with the InfiniBand specification, 
>>
>> I think this is a grey area.
> 
> I agree. However, I thought with SRIOV support and MKey support it was worth
mentioning this.

For SRIOV (guests), the only diags are ibstat and ibstatus right now.
Should there be a separate guest package with just those and their man
pages ?

-- Hal

> 
> Ira
> 
>>
>> -- Hal
>>
>>> practical experience has found
>>> +that this level of diagnostics is valuable when working with a fabric which is
>>> +broken or only partially configured.  For this reason many of these tools may
>>> +require the use of an MKey or operation from Virtual Machines may be restricted
>>> +for security reasons.
>>> +
>>> +
>>>  COMMON OPTIONS
>>>  ==============
>>>  
>>
> 
> 

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