From: Jiri Pirko <jiri@mellanox.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: Sven Eckelmann <sven@narfation.org>,
"b.a.t.m.a.n@lists.open-mesh.org"
<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 v2] batman-adv: Add multicast-to-unicast support for multiple targets
Date: Thu, 14 Feb 2019 14:16:06 +0000 [thread overview]
Message-ID: <20190214140633.GI2363@nanopsycho> (raw)
In-Reply-To: <20190214134452.GA1602@otheros>
Thu, Feb 14, 2019 at 02:44:52PM CET, linus.luessing@c0d3.blue wrote:
>On Thu, Feb 14, 2019 at 01:46:35PM +0100, Sven Eckelmann wrote:
>> On Thursday, 14 February 2019 13:43:01 CET Linus Lüssing wrote:
>> >
>> > +What: /sys/class/net/<mesh_iface>/mesh/multicast_fanout
>> > +Date: Feb 2019
>> > +Contact: Linus Lüssing <linus.luessing@c0d3.blue>
>> > +Description:
>> > + Defines the maximum number of packet copies that may
>> > + be generated for a multicast-to-unicast conversion.
>> > + Once this limit is exceeded distribution will fall
>> > + back to broadcast.
>> > +
>>
>> No new sysfs config files.
>
>Why? The bridge for instance does the same.
I would recommend to add new options only to netlink to force userspace
tools to use it and eventually phase-out sysfs usage..
prev parent reply other threads:[~2019-02-14 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 12:43 [B.A.T.M.A.N.] [PATCH v2] batman-adv: Add multicast-to-unicast support for multiple targets Linus Lüssing
2019-02-14 12:46 ` Sven Eckelmann
2019-02-14 13:44 ` Linus Lüssing
2019-02-14 14:04 ` Sven Eckelmann
2019-02-15 17:20 ` Linus Lüssing
2019-02-14 14:16 ` Jiri Pirko [this message]
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=20190214140633.GI2363@nanopsycho \
--to=jiri@mellanox.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
--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.