From: roopa <roopa@cumulusnetworks•com>
To: Sowmini Varadhan <sowmini.varadhan@oracle•com>
Cc: David Miller <davem@davemloft•net>,
netdev@vger•kernel.org, raghavendra.kt@linux•vnet.ibm.com
Subject: Re: IFLA_INET6_[ICMP6]STATS
Date: Thu, 10 Sep 2015 08:43:58 -0700 [thread overview]
Message-ID: <55F1A53E.1010908@cumulusnetworks.com> (raw)
In-Reply-To: <20150909214528.GE20544@oracle.com>
On 9/9/15, 2:45 PM, Sowmini Varadhan wrote:
> On (09/09/15 14:43), David Miller wrote:
>> 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.
>>
> Yes, interestingly that's what I was experimenting with myself
> (though I was using a setsockopt in my version). I'll send out
> a patch rfc later this week for this.
>
If you decide to use a flag, there is IFLA_EXT_MASK which is used to
specify such filters from userspace today.
/* New extended info filters for IFLA_EXT_MASK */
#define RTEXT_FILTER_VF (1 << 0)
#define RTEXT_FILTER_BRVLAN (1 << 1)
#define RTEXT_FILTER_BRVLAN_COMPRESSED (1 << 2)
ideally long term, it would be nice for RTM_GETLINK request msg to
contain the attributes it is interested in (This would again be
optional with the default being get all attributes).
next prev parent reply other threads:[~2015-09-10 15:44 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 ` roopa [this message]
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 ` IFLA_INET6_[ICMP6]STATS Raghavendra K T
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=55F1A53E.1010908@cumulusnetworks.com \
--to=roopa@cumulusnetworks$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=raghavendra.kt@linux$(echo .)vnet.ibm.com \
--cc=sowmini.varadhan@oracle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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