mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, dsahern@gmail.com, jiri@resnulli.us,
	cphealy@gmail.com, andrew@lunn.ch, jakub.kicinski@netronome.com,
	decot@googlers.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	daniel@iogearbox.net, nikolay@cumulusnetworks.com, ast@fb.com,
	roopa@cumulusnetworks.com, vyasevich@gmail.com,
	jonas@southpole.se, maheshb@google.com,
	stephen@networkplumber.org, ishkamiel@gmail.com, fw@strlen.de,
	arvind.yadav.cs@gmail.com, avagin@openvz.org, mingo@kernel.org,
	lucien.xin@gmail.com, mschiffer@universe-factory.net,
	jbenc@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: core: Expose number of link up/down transitions
Date: Mon, 22 Jan 2018 15:43:18 -0500 (EST)	[thread overview]
Message-ID: <20180122.154318.784941022568373440.davem@davemloft.net> (raw)
In-Reply-To: <20180118175921.17645-1-f.fainelli@gmail.com>

From: Florian Fainelli <f.fainelli@gmail.com>
Date: Thu, 18 Jan 2018 09:59:13 -0800

> From: David Decotigny <decot@googlers.com>
> 
> Expose the number of times the link has been going UP or DOWN, and
> update the "carrier_changes" counter to be the sum of these two events.
> While at it, also update the sysfs-class-net documentation to cover:
> carrier_changes (3.15), carrier_up_count (4.16) and carrier_down_count
> (4.16)
> 
> Signed-off-by: David Decotigny <decot@googlers.com>
> [Florian:
> * rebase
> * add documentation
> * merge carrier_changes with up/down counters]
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Changes in v2:
> - fixed sysfs attributes to use <iface>
> - renamed count_link_{up,down} to carrier_{up,down}_count to match
>   existing carrier_changes semantics

Like David Ahern I am strongly against the proliferation of sysfs files
attached to network devices and the per-netdevice costs associated with
that.

However, dealing with that is a longer term issue that nobody has a clear
plan for.  Therefore I cannot reject this change on that basis alone.

The information is useful, so applied, thanks.

  reply	other threads:[~2018-01-22 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 17:59 Florian Fainelli
2018-01-22 20:43 ` David Miller [this message]
2018-01-22 20:46   ` Florian Fainelli
2018-01-22 22:16     ` lightweight netdevs Jan 2018 edition [Re: [PATCH net-next v2] net: core: Expose number of link up/down transitions] David Ahern

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=20180122.154318.784941022568373440.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=ast@fb.com \
    --cc=avagin@openvz.org \
    --cc=cphealy@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=decot@googlers.com \
    --cc=dsahern@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=ishkamiel@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jbenc@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=maheshb@google.com \
    --cc=mingo@kernel.org \
    --cc=mschiffer@universe-factory.net \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.com \
    --cc=stephen@networkplumber.org \
    --cc=vyasevich@gmail.com \
    --cc=xiyou.wangcong@gmail.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®