[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5555AEE5.9060503@profitbricks.com>
Date: Fri, 15 May 2015 10:31:33 +0200
From: Michael Wang <yun.wang@...fitbricks.com>
To: "Hefty, Sean" <sean.hefty@...el.com>,
Doug Ledford <dledford@...hat.com>
CC: Roland Dreier <roland@...nel.org>,
Hal Rosenstock <hal@....mellanox.co.il>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
"Weiny, Ira" <ira.weiny@...el.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Subject: Re: [PATCH RFC] Documentation/infiniband: Add docs for rdma-helpers
On 05/13/2015 06:42 PM, Hefty, Sean wrote:
>>> + rdma_cap_ib_cm
>>> + ---------------
>>> + Communication Manager (CM) will handle the connections between
>> ^Connection Manager (CM) service, used to ease the process of
>
> In IB terms, this is communication manager. It also handles transport level address resolution for UD QPs.
I could find both 'connection' and 'communication' in different docs,
while 'connection' is more related to verbs, 'communication' is more
close to specification.
IMHO 'connection' make more sense, after all, all the transport between
adaptors could named as communication, while connection management is exactly
what CM did in kernel.
Doug, what's your opinion?
>
>>> + rdma_cap_eth_ah
>>> + ---------------
>>> + Infiniband address handler format is special in ethernet fabric,
>> use
>>> + the helper to verify whether the port is using ethernet format or
>> not.
>>
>> This helper is true when the address of the specific connection is of
>> the Ethernet (RoCE) variety.
>
> This is used for connectionless communication.
Could you please give more details on this?
Regards,
Michael Wang
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists