All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org, David Bauer <mail@david-bauer.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH v4] batman-adv: Add multicast-to-unicast support for multiple targets
Date: Sat, 23 Mar 2019 04:47:34 +0100	[thread overview]
Message-ID: <20190323034734.GF22805@otheros> (raw)
In-Reply-To: <1866651.s4yD58eI2F@sven-edge>

On Sun, Mar 17, 2019 at 11:11:10AM +0100, Sven Eckelmann wrote:
> I am also not sure what in mind here for the limit? The only thing
> which comes to my mind right now is that we have a fanout of something
> low (16) and the precondition test succeeded because it can only find 16 
> entries. And in the meantime, 100 or more new entries are added. In this 
> situation, you would only send to 32 neighbors, right?

Right, that's the situation I had in mind. If the number of
transmissions were growing too large somehow to limit them.

On the other hand, now that you reiterate this maybe this is such
a minor case that it is not worth bothering for now.

Hm, I think I'll remove these intermediate limit checks to
simplify things. So that we only check once in batadv_mcast_forw_mode()
for the mcast_fanout.

  reply	other threads:[~2019-03-23  3:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 21:50 [B.A.T.M.A.N.] [PATCH v4] batman-adv: Add multicast-to-unicast support for multiple targets Linus Lüssing
2019-03-17 10:11 ` Sven Eckelmann
2019-03-23  3:47   ` Linus Lüssing [this message]
2019-03-17 10:13 ` Sven Eckelmann

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=20190323034734.GF22805@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mail@david-bauer.net \
    --cc=sven@narfation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.