From: Phil Sutter <phil@nwl.cc>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: "Pablo Neira Ayuso" <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org,
"Florian Westphal" <fw@strlen.de>,
"Kadlecsik József" <kadlec@blackhole.kfki.hu>,
"Eric Garver" <eric@garver.life>
Subject: Re: [PATCH nft v5] tests: Introduce test for set with concatenated ranges
Date: Fri, 14 Feb 2020 17:02:06 +0100 [thread overview]
Message-ID: <20200214160206.GQ20005@orbyte.nwl.cc> (raw)
In-Reply-To: <546dccfe97760ba910676b84799b15d38164e192.1581693171.git.sbrivio@redhat.com>
On Fri, Feb 14, 2020 at 04:27:25PM +0100, Stefano Brivio wrote:
> This test checks that set elements can be added, deleted, that
> addition and deletion are refused when appropriate, that entries
> time out properly, and that they can be fetched by matching values
> in the given ranges.
>
> v5:
> - speed this up by performing the timeout test for one single
> permutation (Phil Sutter), by decreasing the number of
> permutations from 96 to 12 if this is invoked by run-tests.sh
> (Pablo Neira Ayuso) and by combining some commands into single
> nft calls where possible: with dash 0.5.8 on AMD Epyc 7351 the
> test now takes 1.8s instead of 82.5s
> - renumber test to 0043, 0042 was added meanwhile
> v4: No changes
> v3:
> - renumber test to 0042, 0041 was added meanwhile
> v2:
> - actually check an IPv6 prefix, instead of specifying everything
> as explicit ranges in ELEMS_ipv6_addr
> - renumber test to 0041, 0038 already exists
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Acked-by: Phil Sutter <phil@nwl.cc>
Thanks!
next prev parent reply other threads:[~2020-02-14 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 15:27 [PATCH nft v5] tests: Introduce test for set with concatenated ranges Stefano Brivio
2020-02-14 16:02 ` Phil Sutter [this message]
2020-02-19 17:53 ` Pablo Neira Ayuso
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=20200214160206.GQ20005@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=eric@garver.life \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sbrivio@redhat.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;
as well as URLs for NNTP newsgroup(s).