[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <573016F1.8050700@cumulusnetworks.com>
Date: Sun, 08 May 2016 21:49:53 -0700
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
CC: stephen@...workplumber.org, netdev@...r.kernel.org,
davem@...emloft.net, edumazet@...gle.com, tgraf@...g.ch,
nicolas.dichtel@...nd.com, nikolay@...ulusnetworks.com
Subject: Re: [PATCH iproute2 net-next] ifstat: move to new RTM_GETSTATS api
On 4/30/16, 8:15 AM, Roopa Prabhu wrote:
> On 4/30/16, 3:21 AM, Jamal Hadi Salim wrote:
>> On 16-04-30 02:41 AM, Roopa Prabhu wrote:
>>> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>>>
>>> This patch modifies ifstat to use the new RTM_GETSTATS api
>>> to query stats from the kernel. In the process this also
>>> moves ifstat to use 64 bit stats.
>> Breaks old kernels? May need to keep backward compat of
>> RTM_NEWLINK and even new main struct for GETSTATS.
> yes, i was wondering about that. v2 coming. If GETSTATS fails, I will fallback to RTM_NEWLINK.
>
sorry abt the delay on this one. I hit a snag and could not get back to it last week.
AFAICS ifstat history file handling today assumes all 32 bit stats.
And to preserve backward compatibility, new ifstat should work with old and
new history files with 32bit and 64 bit stats.
The file format cannot be changed because of the same backward compat issues.
So, I am leaning towards a new history file with a new option (maybe ifstat -64) to
save/query 64 bit stats using the new api when available.
I see some previous brief discussions on moving ifstat to 64 bit.
The other option is to only change 'ip -s link show' to use the new stats api.
let me know if there are other thoughts.
thanks,
Roopa
Powered by blists - more mailing lists