Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Christopher Lameter <cl@linux.com>
To: Honggang LI <honli@redhat.com>
Cc: "Håkon Bugge" <haakon.bugge@oracle.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Mark Haywood" <mark.haywood@oracle.com>,
	"OFED mailing list" <linux-rdma@vger.kernel.org>
Subject: Re: Is there a working cache for path record and lids etc for librdmacm?
Date: Wed, 25 Nov 2020 16:43:51 +0000 (UTC)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2011251632300.298485@www.lameter.com> (raw)
In-Reply-To: <20201125081057.GA547111@dhcp-128-72.nay.redhat.com>

On Wed, 25 Nov 2020, Honggang LI wrote:

> > How do I figure out why ibacm is not talking to the subnet manager?
>
> No, you can't talking to subnet manager, if you resolve IPoIB IP address
> or hostname to PathRecord. The query MAD packets will be send to one
> multicast group all ibacm service attached.

Huh? When does it talk to a subnet manager (or the SA)?

If its get an IP address of an IB node that does not have ibacm then it
fails with a timeout ..... ? And leaves hanging kernel threads around by
design?

So it only populates the cache from its local node information?

> To resolve IPoIB address to PathRecord, you must:
> 1) The IPoIB interface must UP and RUNNING on the client and target
> side.
> 2) The ibacm service must RUNNING on the client and target.

That is working if you want to resolve only the IP addresses of the IB
interfaces on the client and target. None else.

Here is the description of ibacms function from the sources:

"Conceptually, the ibacm service implements an ARP like protocol and
either uses IB multicast records to construct path record data or queries
the SA directly, depending on the selected route protocol. By default, the
ibacm services uses and caches SA path record queries."

SA queries dont work. So its broken and cannot talk to the SM.



  reply	other threads:[~2020-11-25 16:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  2:57 Is there a working cache for path record and lids etc for librdmacm? Christopher Lameter
2020-11-17  8:46 ` Jens Domke
2020-11-17 14:20   ` Christopher Lameter
2020-11-17 19:33 ` Jason Gunthorpe
2020-11-20 18:05   ` Christopher Lameter
2020-11-20 18:34     ` Håkon Bugge
2020-11-22 12:49       ` Christopher Lameter
2020-11-22 15:50         ` Håkon Bugge
2020-11-22 19:22           ` Christopher Lameter
2020-11-23 12:50             ` Christopher Lameter
2020-11-23 19:01               ` Håkon Bugge
2020-11-24 19:01                 ` Christopher Lameter
2020-11-25  8:10                   ` Honggang LI
2020-11-25 16:43                     ` Christopher Lameter [this message]
2020-11-27 14:52                       ` Håkon Bugge
2020-11-30  8:24                         ` Christopher Lameter
2020-12-04 11:17                           ` Håkon Bugge
2020-12-05 11:50                             ` Christoph Lameter
2020-12-07 10:28                             ` Christoph Lameter
2020-12-07 21:08                               ` Mark Haywood
2020-12-08  8:59                                 ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2011251632300.298485@www.lameter.com \
    --to=cl@linux.com \
    --cc=haakon.bugge@oracle.com \
    --cc=honli@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mark.haywood@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox