From: Matthias Schiffer <mschiffer@universe-factory.net>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com,
Matthias Schiffer <mschiffer@universe-factory.net>
Subject: [PATCH net-next 0/2] Implement get_link_ksettings for VXLAN and bridge
Date: Sat, 9 Nov 2019 18:54:12 +0100 [thread overview]
Message-ID: <cover.1573321597.git.mschiffer@universe-factory.net> (raw)
Mesh routing protocol batman-adv (in particular the new BATMAN_V algorithm)
uses the link speed reported by get_link_ksettings to determine a path
metric for wired links. In the mesh framework Gluon [1], we layer VXLAN
and sometimes bridge interfaces on our Ethernet links.
These patches implement get_link_ksettings for these two interface types.
While this is obviously not accurate for bridges with multiple active
ports, it's much better than having no estimate at all (and in the
particular setup of Gluon, bridges with a single port aren't completely
uncommon).
[1] https://github.com/freifunk-gluon/gluon
Matthias Schiffer (2):
vxlan: implement get_link_ksettings ethtool method
bridge: implement get_link_ksettings ethtool method
drivers/net/vxlan.c | 24 ++++++++++++++++++++++--
net/bridge/br_device.c | 37 +++++++++++++++++++++++++++++++++++--
2 files changed, 57 insertions(+), 4 deletions(-)
--
2.24.0
next reply other threads:[~2019-11-09 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 17:54 Matthias Schiffer [this message]
2019-11-09 17:54 ` [PATCH net-next 1/2] vxlan: implement get_link_ksettings ethtool method Matthias Schiffer
2019-11-09 17:54 ` [PATCH net-next 2/2] bridge: " Matthias Schiffer
2019-11-11 22:15 ` Nikolay Aleksandrov
2019-11-11 22:41 ` David Miller
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=cover.1573321597.git.mschiffer@universe-factory.net \
--to=mschiffer@universe-factory.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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
all inboxes | Powered by JetHome®