From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>,
Or Gerlitz <gerlitz.or-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] Expire sendonly joins (was Re: [PATCH rdma-rc 0/2] Add mechanism for ipoib neigh state change notifications)
Date: Mon, 28 Sep 2015 11:10:07 -0600 [thread overview]
Message-ID: <20150928171007.GE12415@obsidianresearch.com> (raw)
In-Reply-To: <56095E6B.60509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Mon, Sep 28, 2015 at 11:36:11AM -0400, Doug Ledford wrote:
> > Also broadcast could cause a unecessary reception event on the NICs of
> > machines that have no interest in this traffic.
>
> This is true. However, I'm trying to balance between several competing
> issues. You also stated the revamped multicast code was adding latency
> and dropped packets into the problem space. Sending over the broadcast
> would help with latency. However, I have an alternative idea for that...
I think your original idea of broadcast immediately and deferred
optimal mlid lookup is the best *functionally* for every case - only
when you enter the very edge world of caring about timing does it make
any difference.
Christoph's needs would probably be better served by giving some API
to control the mlid cache (ie the neightbour table is already 99% of
the way there). This would let some userspace component pre-load and
fix all relevant data and undesired cache activity simply can't add
jitter.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-09-28 17:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 10:38 [PATCH rdma-rc 0/2] Add mechanism for ipoib neigh state change notifications Or Gerlitz
[not found] ` <1442486283-9699-1-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-09-17 10:38 ` [PATCH rdma-rc 1/2] IB/ipoib: " Or Gerlitz
2015-09-17 10:38 ` [PATCH rdma-rc 2/2] IB/ipoib: Add cleanup to sendonly multicast objects Or Gerlitz
[not found] ` <1442486283-9699-3-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-09-17 11:19 ` Or Gerlitz
2015-09-17 14:42 ` [PATCH rdma-rc 0/2] Add mechanism for ipoib neigh state change notifications Christoph Lameter
[not found] ` <alpine.DEB.2.11.1509170940270.2052-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-17 18:55 ` Or Gerlitz
2015-09-17 18:57 ` Or Gerlitz
[not found] ` <CAJ3xEMg-h+J=cr2ddWvYUGU=MOBk4Aw-KtkeJutATH0Y17dnjg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-24 17:00 ` [PATCH] Expire sendonly joins (was Re: [PATCH rdma-rc 0/2] Add mechanism for ipoib neigh state change notifications) Christoph Lameter
[not found] ` <alpine.DEB.2.20.1509241158420.21198-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-25 15:32 ` Or Gerlitz
[not found] ` <CAJ3xEMg2qQ3CXrfTrg=gUX2tQRuPnpxA-8PC98GzoF5iz=j5PQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-25 16:41 ` Christoph Lameter
[not found] ` <alpine.DEB.2.20.1509251140200.31792-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-25 16:55 ` Christoph Lameter
2015-09-26 17:35 ` Or Gerlitz
[not found] ` <CAJ3xEMj9kGaM6s+AqBQ_-ZTB_+cgDk3kefhq_O0V3PM120O9yQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-27 16:39 ` Christoph Lameter
[not found] ` <alpine.DEB.2.20.1509271136570.14486-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-27 17:32 ` Doug Ledford
[not found] ` <5608282F.1020507-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-28 2:28 ` Christoph Lameter
[not found] ` <alpine.DEB.2.20.1509272120090.18678-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-28 15:36 ` Doug Ledford
[not found] ` <56095E6B.60509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-28 15:51 ` Christoph Lameter
[not found] ` <alpine.DEB.2.20.1509281046440.30710-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-28 16:59 ` Doug Ledford
[not found] ` <560971DC.500-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-28 17:05 ` Christoph Lameter
2015-09-28 17:11 ` Christoph Lameter
2015-09-28 17:10 ` Jason Gunthorpe [this message]
[not found] ` <20150928171007.GE12415-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-09-28 17:19 ` Christoph Lameter
[not found] ` <alpine.DEB.2.20.1509281217470.31260-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-09-28 17:36 ` Jason Gunthorpe
2015-09-29 17:47 ` Doug Ledford
2015-09-28 6:37 ` Or Gerlitz
[not found] ` <CAJ3xEMg5aC8oeBVA9qygVJyLd2GM9C4sVLZqAL=kFGBcgBq_oQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-28 11:17 ` 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=20150928171007.GE12415@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=gerlitz.or-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).