From: David Miller <davem@davemloft.net>
To: daniel@zonque.org
Cc: ast@fb.com, dh.herrmann@gmail.com, daniel@iogearbox.net,
netdev@vger.kernel.org
Subject: Re: [PATCH v1 0/2] bpf: add longest prefix match map
Date: Fri, 30 Dec 2016 15:25:36 -0500 (EST) [thread overview]
Message-ID: <20161230.152536.1044375840168125040.davem@davemloft.net> (raw)
In-Reply-To: <20161229172855.14910-1-daniel@zonque.org>
From: Daniel Mack <daniel@zonque.org>
Date: Thu, 29 Dec 2016 18:28:53 +0100
> This patch set adds a longest prefix match algorithm that can be used
> to match IP addresses to a stored set of ranges. It is exposed as a
> bpf map type.
>
> Internally, data is stored in an unbalanced tree of nodes that has a
> maximum height of n, where n is the prefixlen the trie was created
> with.
>
> Not that this has nothing to do with fib or fib6 and is in no way meant
> to replace or share code with it. It's rather a much simpler
> implementation that is specifically written with bpf maps in mind.
>
> Patch 1/2 adds the implementation, and 2/2 an extensive test suite.
>
> Feedback is much appreciated.
I'll give Alexei and Daniel time to provide feedback on this series.
next prev parent reply other threads:[~2016-12-30 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 17:28 [PATCH v1 0/2] bpf: add longest prefix match map Daniel Mack
2016-12-29 17:28 ` [PATCH v1 1/2] bpf: add a longest prefix match trie map implementation Daniel Mack
2017-01-05 16:25 ` Daniel Borkmann
2017-01-05 16:40 ` Daniel Borkmann
2017-01-05 20:01 ` Daniel Borkmann
2017-01-05 20:14 ` Daniel Mack
2017-01-06 10:43 ` Daniel Borkmann
2017-01-06 19:59 ` Alexei Starovoitov
2017-01-05 20:04 ` Daniel Mack
2017-01-05 20:20 ` Daniel Borkmann
2016-12-29 17:28 ` [PATCH v1 2/2] bpf: Add tests for the lpm trie map Daniel Mack
2016-12-30 20:25 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-31 22:31 [PATCH v1 0/2] bpf: add longest prefix match map Alexei Starovoitov
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=20161230.152536.1044375840168125040.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).