From: Scott Feldman <sfeldma@gmail.com>
To: anuradhak@cumulusnetworks.com
Cc: "David S. Miller" <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>,
Wilson Kok <wkok@cumulusnetworks.com>
Subject: Re: [RFC PATCH net-next v3 0/4] net: Introduce IFF_PROTO_DOWN flag.
Date: Mon, 27 Apr 2015 22:45:46 -0700 [thread overview]
Message-ID: <CAE4R7bAGRKGShQuSqjvQDW8cG6MHE8Jie7Hp=7FJw00kJM4NgQ@mail.gmail.com> (raw)
In-Reply-To: <1430156304-13187-1-git-send-email-anuradhak@cumulusnetworks.com>
On Mon, Apr 27, 2015 at 10:38 AM, <anuradhak@cumulusnetworks.com> wrote:
> From: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
>
> User space daemons can detect errors in the network that need to be
> notified to the switch device drivers.
>
> Drivers can react to this error state by doing a phy-down on the
> switch-port which would result in a carrier-off locally and on the
> directly connected switch. Doing that would prevent loops and
> black-holes in the network.
(Sorry if this was asked earlier)
Can the application simply send a SETLINK with IFF_UP clear and the
port driver's ndo_stop would bring the PHY link down?
next prev parent reply other threads:[~2015-04-28 5:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:38 [RFC PATCH net-next v3 0/4] net: Introduce IFF_PROTO_DOWN flag anuradhak
2015-04-28 5:45 ` Scott Feldman [this message]
2015-04-28 15:43 ` Anuradha Karuppiah
[not found] ` <CACcJQnRw5HVUb0M3A2u_zbMtp85pi+kdCUa5gaY6cN4HXpVyeQ@mail.gmail.com>
2015-04-28 19:37 ` Scott Feldman
2015-04-28 20:04 ` Anuradha Karuppiah
2015-04-29 0:28 ` Scott Feldman
2015-04-29 22:04 ` Anuradha Karuppiah
2015-04-29 22:08 ` Stephen Hemminger
2015-04-29 22:58 ` Anuradha Karuppiah
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='CAE4R7bAGRKGShQuSqjvQDW8cG6MHE8Jie7Hp=7FJw00kJM4NgQ@mail.gmail.com' \
--to=sfeldma@gmail.com \
--cc=anuradhak@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=wkok@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;
as well as URLs for NNTP newsgroup(s).