From: Stephen Suryaputra <ssuryaextr@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Yogesh Ankolekar <ayogesh@juniper.net>,
Girish Kumar S <girik@juniper.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Linux Ipv6 stats support
Date: Mon, 8 Mar 2021 23:44:24 -0500 [thread overview]
Message-ID: <20210309044424.GA11084@ICIPI.localdomain> (raw)
In-Reply-To: <a1c21b7c-c345-0f05-2db1-3f94a2ad4f6a@gmail.com>
On Tue, Jan 26, 2021 at 09:05:22AM -0700, David Ahern wrote:
> On 1/25/21 4:26 AM, Yogesh Ankolekar wrote:
> >
> > We are looking for below IPv6 stats support in linux. Looks below
> > stats are not supported. Will these stats will be supported in future or
> > it is already supported in some version. Please guide.
>
> I am not aware of anyone working on adding more stats for IPv6. Stephen
> Suryaputra attempted to add stats a few years back as I believe the
> resistance was around memory and cpu usage for stats in the hot path.
Sorry that I missed this. At that time it was IPv4 ifstats. I'm missing
the rest of the context here. Which IPv6 stats are being discussed here?
For my company, we have been doing the v4 stats using the implementation
that I brought up to netdev then. It is useful to debug forwarding
errors but it is an overhead having the out of tree patch everytime
kernel upgrade is needed, esp on upgrade to a major version.
Thank you,
Stephen.
next prev parent reply other threads:[~2021-03-09 4:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR05MB7557A2136390919FB11B6714AAA09@PH0PR05MB7557.namprd05.prod.outlook.com>
[not found] ` <PH0PR05MB755758D4F271A5DB8897864AAABD9@PH0PR05MB7557.namprd05.prod.outlook.com>
[not found] ` <PH0PR05MB77013792D0D90212B1AA0D9EBABD9@PH0PR05MB7701.namprd05.prod.outlook.com>
2021-01-26 16:05 ` Linux Ipv6 stats support David Ahern
2021-03-09 4:44 ` Stephen Suryaputra [this message]
2021-03-09 7:37 ` Girish Kumar S
2021-03-09 14:01 ` Stephen Suryaputra
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=20210309044424.GA11084@ICIPI.localdomain \
--to=ssuryaextr@gmail.com \
--cc=ayogesh@juniper.net \
--cc=dsahern@gmail.com \
--cc=girik@juniper.net \
--cc=netdev@vger.kernel.org \
/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