From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>, sowmini.varadhan@oracle.com
Cc: netdev@vger.kernel.org
Subject: Re: IFLA_INET6_[ICMP6]STATS
Date: Thu, 10 Sep 2015 20:49:43 +0530 [thread overview]
Message-ID: <55F19F8F.4080407@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150909.144308.360246374222280540.davem@davemloft.net>
On 09/10/2015 03:13 AM, David Miller wrote:
> From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
> Date: Wed, 9 Sep 2015 17:34:44 -0400
>
>> So the question is- who uses IFLA_INET6_STATS/IFLA_INET6_ICMP6STATS?
>> Is this intended for some ND/ripngd etc daemon? Doesnt seem to
>> be documented in rtnetlink(7), and couldnt find any users in glibc,
>> and google did not find any usage.
>
> It doesn't really matter who uses it, it's there forever and we
> therefore can't remove it.
>
> But what we could do is add a flag in the netlink request which
> elides the stats. GLIBC et al. could then start setting the flag.
>
+1 for this. Had similar thought. Wanted to use a flag at the higher
level function to avoid snmp stat walk through during i/f creation.
But above idea is better.
Other idea I had was to defer the update using work queue/completion
etc..
next prev parent reply other threads:[~2015-09-10 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 21:34 IFLA_INET6_[ICMP6]STATS Sowmini Varadhan
2015-09-09 21:43 ` IFLA_INET6_[ICMP6]STATS David Miller
2015-09-09 21:45 ` IFLA_INET6_[ICMP6]STATS Sowmini Varadhan
2015-09-10 15:43 ` IFLA_INET6_[ICMP6]STATS roopa
2015-09-10 15:48 ` IFLA_INET6_[ICMP6]STATS Sowmini Varadhan
2015-09-10 17:13 ` IFLA_INET6_[ICMP6]STATS David Miller
2015-09-10 17:16 ` IFLA_INET6_[ICMP6]STATS Sowmini Varadhan
2015-09-10 17:20 ` IFLA_INET6_[ICMP6]STATS David Miller
2015-09-10 15:19 ` Raghavendra K T [this message]
2015-09-09 23:00 ` IFLA_INET6_[ICMP6]STATS Eric Dumazet
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=55F19F8F.4080407@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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).