From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Decotigny <decot@googlers.com>,
"David S. Miller" <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Eric Dumazet <edumazet@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Weilong Chen <chenweilong@huawei.com>,
Jiri Pirko <jiri@resnulli.us>, Amir Vadai <amirv@mellanox.com>,
Michael Dalton <mwdalton@google.com>,
Al Viro <viro@ZenIV.linux.org.uk>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH net-next v2] net-sysfs: expose number of carrier on/off changes
Date: Sat, 29 Mar 2014 18:50:45 -0700 [thread overview]
Message-ID: <1396144245.29410.2.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20140329183628.509f1239@nehalam.linuxnetplumber.net>
On Sat, 2014-03-29 at 18:36 -0700, Stephen Hemminger wrote:
> On Sat, 29 Mar 2014 09:48:35 -0700
> David Decotigny <decot@googlers.com> wrote:
>
> > This allows to monitor carrier on/off transitions and detect link
> > flapping issues:
> > - new /sys/class/net/X/carrier_changes
> > - new rtnetlink IFLA_CARRIER_CHANGES (getlink)
> >
> > Tested:
> > - grep . /sys/class/net/*/carrier_changes
> > + ip link set dev X down/up
> > + plug/unplug cable
> > - updated iproute2: prints IFLA_CARRIER_CHANGES
> > - iproute2 20121211-2 (debian): unchanged behavior
> >
> > Signed-off-by: David Decotigny <decot@googlers.com>
>
> Is there a related SNMP MIB variable? should there be?
I don't think we have any SNMP MIB variable for devices ?
It seems "ip link" is the facto standard.
(BTW we put BusyPollRxPackets in TcpExt group, this was an error IMHO)
next prev parent reply other threads:[~2014-03-30 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1396111568.git.decot@googlers.com>
2014-03-29 16:48 ` David Decotigny
2014-03-30 1:36 ` Stephen Hemminger
2014-03-30 1:50 ` Eric Dumazet [this message]
2014-03-30 15:18 ` David Decotigny
2014-03-31 16:49 ` Florian Fainelli
2014-03-31 20:25 ` 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=1396144245.29410.2.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=amirv@mellanox.com \
--cc=chenweilong@huawei.com \
--cc=davem@davemloft.net \
--cc=decot@googlers.com \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mwdalton@google.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tj@kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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®