mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mschiffer@universe-factory.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com
Subject: Re: [PATCH net-next v2 0/2] Implement get_link_ksettings for VXLAN and bridge
Date: Tue, 12 Nov 2019 19:52:30 -0800 (PST)	[thread overview]
Message-ID: <20191112.195230.1255959947276169668.davem@davemloft.net> (raw)
In-Reply-To: <cover.1573591594.git.mschiffer@universe-factory.net>

From: Matthias Schiffer <mschiffer@universe-factory.net>
Date: Tue, 12 Nov 2019 22:12:23 +0100

> 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

Series applied, thanks.


      parent reply	other threads:[~2019-11-13  3:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 21:12 Matthias Schiffer
2019-11-12 21:12 ` [PATCH net-next v2 1/2] vxlan: implement get_link_ksettings ethtool method Matthias Schiffer
2019-11-12 21:12 ` [PATCH net-next v2 2/2] bridge: " Matthias Schiffer
2019-11-13  3:52 ` David Miller [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=20191112.195230.1255959947276169668.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschiffer@universe-factory.net \
    --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®