From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
magnus.karlsson@intel.com, bjorn@kernel.org,
weqaar.a.janjua@intel.com
Subject: Re: [PATCH bpf-next 1/4] selftest/bpf: make xsk tests less verbose
Date: Mon, 22 Feb 2021 12:58:03 +0100 [thread overview]
Message-ID: <20210222115803.GC29106@ranger.igk.intel.com> (raw)
In-Reply-To: <20210217160214.7869-2-ciara.loftus@intel.com>
On Wed, Feb 17, 2021 at 04:02:11PM +0000, Ciara Loftus wrote:
> From: Magnus Karlsson <magnus.karlsson@intel.com>
>
> Make the xsk tests less verbose by only printing the
> essentials. Currently, it is hard to see if the tests passed or not
> due to all the printouts. Move the extra printouts to a verbose
> option, if further debugging is needed when a problem arises.
>
> To run the xsk tests with verbose output:
> ./test_xsk.sh -v
>
> Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Acked-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
next prev parent reply other threads:[~2021-02-22 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 16:02 [PATCH bpf-next 0/4] selftests/bpf: xsk improvements and new stats tests Ciara Loftus
2021-02-17 16:02 ` [PATCH bpf-next 1/4] selftest/bpf: make xsk tests less verbose Ciara Loftus
2021-02-22 11:58 ` Maciej Fijalkowski [this message]
2021-02-17 16:02 ` [PATCH bpf-next 2/4] selftests/bpf: expose debug arg to shell script for xsk tests Ciara Loftus
2021-02-19 13:12 ` Magnus Karlsson
2021-02-22 14:29 ` Loftus, Ciara
2021-02-17 16:02 ` [PATCH bpf-next 3/4] selftests/bpf: restructure xsk selftests Ciara Loftus
2021-02-18 9:33 ` Björn Töpel
2021-02-22 11:23 ` Maciej Fijalkowski
2021-02-23 8:24 ` Loftus, Ciara
2021-02-17 16:02 ` [PATCH bpf-next 4/4] selftests/bpf: introduce xsk statistics tests Ciara Loftus
2021-02-22 11:56 ` Maciej Fijalkowski
2021-02-22 14:33 ` Loftus, Ciara
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=20210222115803.GC29106@ranger.igk.intel.com \
--to=maciej.fijalkowski@intel.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ciara.loftus@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=weqaar.a.janjua@intel.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).