From: Jason Gunthorpe <jgg@ziepe.ca>
To: Christopher Lameter <cl@linux.com>,
Haakon Bugge <haakon.bugge@oracle.com>,
Mark Haywood <mark.haywood@oracle.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: Is there a working cache for path record and lids etc for librdmacm?
Date: Tue, 17 Nov 2020 15:33:29 -0400 [thread overview]
Message-ID: <20201117193329.GH244516@ziepe.ca> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2011170253150.206345@www.lameter.com>
On Tue, Nov 17, 2020 at 02:57:57AM +0000, Christopher Lameter wrote:
> We have a large number of apps running on the same host that are all
> sending to the same set of hosts. Lots of requests for address resolution
> are going to the SM and for a large set of hosts this can become too much
> for the SM.
>
> Is there something that can locally cache the results of the SM queries to
> avoid additional requests?
>
> We have tried IBACM but the address resolution does not work on it. It is
> unable to complete a request for any address resolution and leaves kernel
> threads that never terminate instead.
If it really doesn't work at all any more we should delete it from
rdma-core if nobody is interested to fix it.
Haakon and Mark had stepped up to maintain it a while ago because they
were using it internally, so I'm surprised to hear it is broken.
Jason
next prev parent reply other threads:[~2020-11-17 19:33 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 [this message]
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
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=20201117193329.GH244516@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=cl@linux.com \
--cc=haakon.bugge@oracle.com \
--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