From: Stefano Brivio <sbrivio@redhat.com>
To: Jie2x Zhou <jie2x.zhou@intel.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
shuah@kernel.org, liuhangbin@gmail.com, fw@strlen.de,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Philip Li <philip.li@intel.com>,
kernel test robot <lkp@intel.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] selftests: netfilter: correct PKTGEN_SCRIPT_PATHS in nft_concat_range.sh
Date: Thu, 16 Jun 2022 15:46:18 +0200 [thread overview]
Message-ID: <20220616154618.0eb6b283@elisabeth> (raw)
In-Reply-To: <Yqr9pQ9QsVaGjNW/@salvia>
Hi Jie2x,
On Thu, 16 Jun 2022 11:53:41 +0200
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> Cc'ing netfilter-devel and Stefano Brivio.
>
> On Thu, Jun 16, 2022 at 03:40:46PM +0800, Jie2x Zhou wrote:
> > Before change:
> > make -C netfilter
> > TEST: performance
> > net,port [SKIP]
> > perf not supported
> > port,net [SKIP]
> > perf not supported
> > net6,port [SKIP]
> > perf not supported
> > port,proto [SKIP]
> > perf not supported
> > net6,port,mac [SKIP]
> > perf not supported
> > net6,port,mac,proto [SKIP]
> > perf not supported
> > net,mac [SKIP]
> > perf not supported
> >
> > After change:
> > net,mac [ OK ]
> > baseline (drop from netdev hook): 2061098pps
> > baseline hash (non-ranged entries): 1606741pps
> > baseline rbtree (match on first field only): 1191607pps
> > set with 1000 full, ranged entries: 1639119pps
> > ok 8 selftests: netfilter: nft_concat_range.sh
> >
> > Fixes: 611973c1e06f ("selftests: netfilter: Introduce tests for sets with range concatenation")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Jie2x Zhou <jie2x.zhou@intel.com>
> > ---
> > tools/testing/selftests/netfilter/nft_concat_range.sh | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/netfilter/nft_concat_range.sh b/tools/testing/selftests/netfilter/nft_concat_range.sh
> > index b35010cc7f6a..a6991877e50c 100755
> > --- a/tools/testing/selftests/netfilter/nft_concat_range.sh
> > +++ b/tools/testing/selftests/netfilter/nft_concat_range.sh
> > @@ -31,7 +31,7 @@ BUGS="flush_remove_add reload"
> >
> > # List of possible paths to pktgen script from kernel tree for performance tests
> > PKTGEN_SCRIPT_PATHS="
> > - ../../../samples/pktgen/pktgen_bench_xmit_mode_netif_receive.sh
> > + ../../../../samples/pktgen/pktgen_bench_xmit_mode_netif_receive.sh
This came from the fact that I used, for testing, to copy the
directories 'samples' and 'selftests' to the root of a filesystem
on a virtual machine, instead of copying the full 'tools' directory.
It was a very arbitrary usage though, also given that 'selftests' is
typically biggest directory in 'tools', so there's no need to keep the
previous path.
Thanks for fixing this,
Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
--
Stefano
prev parent reply other threads:[~2022-06-16 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220616074046.49349-1-jie2x.zhou@intel.com>
2022-06-16 9:53 ` [PATCH] selftests: netfilter: correct PKTGEN_SCRIPT_PATHS in nft_concat_range.sh Pablo Neira Ayuso
2022-06-16 13:46 ` Stefano Brivio [this message]
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=20220616154618.0eb6b283@elisabeth \
--to=sbrivio@redhat.com \
--cc=fw@strlen.de \
--cc=jie2x.zhou@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lkp@intel.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=philip.li@intel.com \
--cc=shuah@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).