From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Daniel Mack <daniel@zonque.org>
Cc: ast@fb.com, dh.herrmann@gmail.com, daniel@iogearbox.net,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH v4 2/3] bpf: Add tests for the lpm trie map
Date: Sun, 22 Jan 2017 14:58:53 -0800 [thread overview]
Message-ID: <20170122225851.GC73160@ast-mbp.thefacebook.com> (raw)
In-Reply-To: <20170121162613.4159-3-daniel@zonque.org>
On Sat, Jan 21, 2017 at 05:26:12PM +0100, Daniel Mack wrote:
> From: David Herrmann <dh.herrmann@gmail.com>
>
> The first part of this program runs randomized tests against the
> lpm-bpf-map. It implements a "Trivial Longest Prefix Match" (tlpm)
> based on simple, linear, single linked lists. The implementation
> should be pretty straightforward.
>
> Based on tlpm, this inserts randomized data into bpf-lpm-maps and
> verifies the trie-based bpf-map implementation behaves the same way
> as tlpm.
>
> The second part uses 'real world' IPv4 and IPv6 addresses and tests
> the trie with those.
>
> Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
> Signed-off-by: Daniel Mack <daniel@zonque.org>
Acked-by: Alexei Starovoitov <ast@kernel.org>
next prev parent reply other threads:[~2017-01-22 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 16:26 [PATCH v4 0/3] bpf: add longest prefix match map Daniel Mack
2017-01-21 16:26 ` [PATCH v4 1/3] bpf: add a longest prefix match trie map implementation Daniel Mack
2017-01-22 22:57 ` Alexei Starovoitov
2017-01-23 16:39 ` Daniel Borkmann
2017-01-23 16:42 ` Daniel Mack
2017-01-21 16:26 ` [PATCH v4 2/3] bpf: Add tests for the lpm trie map Daniel Mack
2017-01-22 22:58 ` Alexei Starovoitov [this message]
2017-01-21 16:26 ` [PATCH v4 3/3] samples/bpf: add lpm-trie benchmark Daniel Mack
2017-01-22 23:02 ` Alexei Starovoitov
2017-01-23 21:11 ` [PATCH v4 0/3] bpf: add longest prefix match map David Miller
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=20170122225851.GC73160@ast-mbp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--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 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.