netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Feldman <sfeldma@gmail.com>
To: Andy Gospodarek <gospo@cumulusnetworks.com>
Cc: Netdev <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	ddutt@cumulusnetworks.com
Subject: Re: [PATCH net-next] net: change fib behavior based on interface link status
Date: Tue, 2 Jun 2015 22:03:23 -0700	[thread overview]
Message-ID: <CAE4R7bDHsoaN6spkOW5jk94wB3wkUBd-j+y3H47611CxZUT6ag@mail.gmail.com> (raw)
In-Reply-To: <1433300839-18511-1-git-send-email-gospo@cumulusnetworks.com>

On Tue, Jun 2, 2015 at 8:07 PM, Andy Gospodarek
<gospo@cumulusnetworks.com> wrote:
> This patch adds the ability to have the Linux kernel track whether or
> not a particular route should be used based on the link-status of the
> interface associated with the next-hop.
>
> Before this patch any link-failure on an interface that was serving as a
> gateway for some systems could result in those systems being isolated
> from the rest of the network as the stack would continue to attempt to
> send frames out of an interface that is actually linked-down.  When the
> kernel is responsible for all forwarding, it should also be responsible
> for taking action when the traffic can no longer be forwarded -- there
> is no real need to outsource link-monitoring to userspace anymore.

Hi Andy, how does this work for the hardware offload case?  I'm not
seeing how hardware gets updated when the software route is updated.
Seems hardware isn't updated and would send frames out the downed nh
interface.

-scott

  reply	other threads:[~2015-06-03  5:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  3:07 [PATCH net-next] net: change fib behavior based on interface link status Andy Gospodarek
2015-06-03  5:03 ` Scott Feldman [this message]
2015-06-03 15:12   ` Andy Gospodarek
2015-06-03 17:40     ` Scott Feldman
2015-06-03 17:57       ` Andy Gospodarek
2015-06-03 18:12         ` Scott Feldman
2015-06-03 18:16           ` Andy Gospodarek
2015-06-03  9:35 ` Hannes Frederic Sowa
2015-06-03 13:49   ` Andy Gospodarek
2015-06-03 13:53 ` Neil Horman
2015-06-03 14:13   ` Hannes Frederic Sowa
2015-06-03 14:21     ` Neil Horman
2015-06-03 14:45       ` Hannes Frederic Sowa
2015-06-03 14:46       ` Andy Gospodarek
2015-06-03 15:02         ` Neil Horman
2015-06-03 15:16           ` Andy Gospodarek
2015-06-03 17:47             ` Neil Horman
2015-06-03 15:17           ` Hannes Frederic Sowa
2015-06-03 14:03 ` Hannes Frederic Sowa
2015-06-03 14:24   ` Andy Gospodarek
2015-06-03 18:15 ` Scott Feldman
2015-06-03 18:27   ` Andy Gospodarek
2015-06-03 19:03     ` Scott Feldman
2015-06-03 20:11       ` Andy Gospodarek
2015-06-03 20:04     ` Hannes Frederic Sowa
2015-06-03 20:34       ` Andy Gospodarek
2015-06-03 20:36         ` Hannes Frederic Sowa
2015-06-03 18:25 ` Alexander Duyck
2015-06-03 20:02   ` Andy Gospodarek
2015-06-03 21:01     ` Alexander Duyck
2015-06-05 19:05       ` Andy Gospodarek

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=CAE4R7bDHsoaN6spkOW5jk94wB3wkUBd-j+y3H47611CxZUT6ag@mail.gmail.com \
    --to=sfeldma@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ddutt@cumulusnetworks.com \
    --cc=gospo@cumulusnetworks.com \
    --cc=netdev@vger.kernel.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).