From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH net-next 0/9] net: Kernel side filtering for route dumps
Date: Thu, 11 Oct 2018 08:26:37 -0700 [thread overview]
Message-ID: <20181011082637.3e7833c9@xeon-e3> (raw)
In-Reply-To: <20181011150627.4010-1-dsahern@kernel.org>
On Thu, 11 Oct 2018 08:06:18 -0700
David Ahern <dsahern@kernel.org> wrote:
> From: David Ahern <dsahern@gmail.com>
>
> Implement kernel side filtering of route dumps by protocol (e.g., which
> routing daemon installed the route), route type (e.g., unicast), table
> id and nexthop device.
>
> iproute2 has been doing this filtering in userspace for years; pushing
> the filters to the kernel side reduces the amount of data the kernel
> sends and reduces wasted cycles on both sides processing unwanted data.
> These initial options provide a huge improvement for efficiently
> examining routes on large scale systems.
>
> David Ahern (9):
> net: Add struct for fib dump filter
> net/ipv4: Plumb support for filtering route dumps
> net/ipv6: Plumb support for filtering route dumps
> net/mpls: Plumb support for filtering route dumps
> net: Plumb support for filtering ipv4 and ipv6 multicast route dumps
> net: Enable kernel side filtering of route dumps
> net/mpls: Handle kernel side filtering of route dumps
> net/ipv6: Bail early if user only wants cloned entries
> net/ipv4: Bail early if user only wants prefix entries
>
> include/linux/mroute_base.h | 5 +--
> include/net/ip6_route.h | 1 +
> include/net/ip_fib.h | 14 ++++++--
> net/ipv4/fib_frontend.c | 64 +++++++++++++++++++++++++++------
> net/ipv4/fib_trie.c | 37 +++++++++++++------
> net/ipv4/ipmr.c | 8 +++--
> net/ipv4/ipmr_base.c | 33 ++++++++++++++++-
> net/ipv6/ip6_fib.c | 17 +++++++--
> net/ipv6/ip6mr.c | 7 ++--
> net/ipv6/route.c | 40 ++++++++++++++++-----
> net/mpls/af_mpls.c | 86 +++++++++++++++++++++++++++++++++++++++------
> 11 files changed, 262 insertions(+), 50 deletions(-)
>
You can do the something like this already with BPF socket filters.
But writing BPF for multi-part messages is hard.
Maybe a generic eBPF filter mechanism would be more flexible?
next prev parent reply other threads:[~2018-10-11 22:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 15:06 [PATCH net-next 0/9] net: Kernel side filtering for route dumps David Ahern
2018-10-11 15:06 ` [PATCH net-next 1/9] net: Add struct for fib dump filter David Ahern
2018-10-11 15:06 ` [PATCH net-next 2/9] net/ipv4: Plumb support for filtering route dumps David Ahern
2018-10-11 15:56 ` Andrew Lunn
2018-10-11 16:44 ` David Ahern
2018-10-11 18:30 ` Andrew Lunn
2018-10-11 15:06 ` [PATCH net-next 3/9] net/ipv6: " David Ahern
2018-10-11 15:06 ` [PATCH net-next 4/9] net/mpls: " David Ahern
2018-10-11 15:06 ` [PATCH net-next 5/9] net: Plumb support for filtering ipv4 and ipv6 multicast " David Ahern
2018-10-11 15:06 ` [PATCH net-next 6/9] net: Enable kernel side filtering of " David Ahern
2018-10-11 15:06 ` [PATCH net-next 7/9] net/mpls: Handle " David Ahern
2018-10-11 15:06 ` [PATCH net-next 8/9] net/ipv6: Bail early if user only wants cloned entries David Ahern
2018-10-11 15:06 ` [PATCH net-next 9/9] net/ipv4: Bail early if user only wants prefix entries David Ahern
2018-10-11 15:26 ` Stephen Hemminger [this message]
2018-10-11 15:32 ` [PATCH net-next 0/9] net: Kernel side filtering for route dumps David Ahern
2018-10-11 16:10 ` Sowmini Varadhan
2018-10-11 16:13 ` David Ahern
2018-10-11 15:46 ` Sowmini Varadhan
2018-10-11 16:07 ` Jamal Hadi Salim
2018-10-11 16:16 ` David Ahern
2018-10-11 16:33 ` Roopa Prabhu
2018-10-11 16:37 ` Sowmini Varadhan
2018-10-11 16:46 ` Jamal Hadi Salim
2018-10-11 17:04 ` David Ahern
2018-10-11 18:05 ` Jamal Hadi Salim
2018-10-11 18:44 ` David Ahern
2018-10-11 19:28 ` David Miller
2018-10-11 19:32 ` Sowmini Varadhan
2018-10-11 19:43 ` David Miller
2018-10-11 19:54 ` Jamal Hadi Salim
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=20181011082637.3e7833c9@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.