Netdev List
 help / color / mirror / Atom feed
From: Stephen Suryaputra <ssuryaextr@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Nikolay Aleksandrov <nikolay@nvidia.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipmr: ip6mr: Add ability to display non default caches and vifs
Date: Mon, 20 Sep 2021 19:49:09 -0400	[thread overview]
Message-ID: <20210920234909.GB5695@ssuryadesk> (raw)
In-Reply-To: <44c43842-2e5a-4e20-b2e6-9f2f2ae6cf0f@gmail.com>

On Wed, Aug 18, 2021 at 06:04:12PM -0600, David Ahern wrote:
> On 8/18/21 5:12 PM, Nikolay Aleksandrov wrote:
> > I do not. You can already use netlink to dump any table, I don't see any point
> > in making those available via /proc, it's not a precedent. We have a ton of other
> > (almost any) information already exported via netlink without any need for /proc,
> > there really is no argument to add this new support.
> 
> agreed. From a routing perspective /proc files are very limiting. You
> really need to be using netlink and table dumps. iproute2 and kernel
> infra exist to efficiently request the dump of a specific table. What is
> missing beyond that?

On this, I realized now that without /proc the multicast caches can be
displayed using iproute2. But, it doesn't seem to have support to
display vifs. Is there a public domain command line utility that can
display vifs on non default table, i.e. the one that uses the support in
the kernel in commit 772c344dbb23 ("net: ipmr: add getlink support")?

Thanks.

  reply	other threads:[~2021-09-21  1:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 20:09 [PATCH net-next] ipmr: ip6mr: Add ability to display non default caches and vifs Stephen Suryaputra
2021-08-18 22:37 ` Nikolay Aleksandrov
2021-08-18 22:50   ` Stephen Suryaputra
2021-08-18 23:09     ` Andrew Lunn
2021-08-18 23:12     ` Nikolay Aleksandrov
2021-08-19  0:04       ` David Ahern
2021-09-20 23:49         ` Stephen Suryaputra [this message]
2021-09-21  7:43           ` Nikolay Aleksandrov

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=20210920234909.GB5695@ssuryadesk \
    --to=ssuryaextr@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.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