From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
Cc: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<netdev@vger.kernel.org>, <magnus.karlsson@intel.com>,
<bjorn@kernel.org>, <kuba@kernel.org>, <andrii@kernel.org>,
<ciara.loftus@intel.com>
Subject: Re: [PATCH bpf-next v4] selftests: xsk: Update poll test cases
Date: Wed, 10 Aug 2022 15:08:14 +0200 [thread overview]
Message-ID: <YvOtvgdSnOhUd9Po@boxer> (raw)
In-Reply-To: <20220803144354.98122-1-shibin.koikkara.reeny@intel.com>
On Wed, Aug 03, 2022 at 02:43:54PM +0000, Shibin Koikkara Reeny wrote:
> Poll test case was not testing all the functionality
> of the poll feature in the testsuite. This patch
> update the poll test case which contain 2 testcases to
updates, contains, test cases
> test the RX and the TX poll functionality and additional
> 2 more testcases to check the timeout features of the
feature
> poll event.
>
> Poll testsuite have 4 test cases:
test suite, has
>
> 1. TEST_TYPE_RX_POLL:
> Check if RX path POLLIN function work as expect. TX path
works
> can use any method to sent the traffic.
send
>
> 2. TEST_TYPE_TX_POLL:
> Check if TX path POLLOUT function work as expect. RX path
> can use any method to receive the traffic.
>
> 3. TEST_TYPE_POLL_RXQ_EMPTY:
> Call poll function with parameter POLLIN on empty rx queue
> will cause timeout.If return timeout then test case is pass.
space after dot
>
> 4. TEST_TYPE_POLL_TXQ_FULL:
> When txq is filled and packets are not cleaned by the kernel
> then if we invoke the poll function with POLLOUT then it
> should trigger timeout.
>
> v1: https://lore.kernel.org/bpf/20220718095712.588513-1-shibin.koikkara.reeny@intel.com/
> v2: https://lore.kernel.org/bpf/20220726101723.250746-1-shibin.koikkara.reeny@intel.com/
> v3: https://lore.kernel.org/bpf/20220729132337.211443-1-shibin.koikkara.reeny@intel.com/
>
> Changes in v2:
> * Updated the commit message
> * fixed the while loop flow in receive_pkts function.
> Changes in v3:
> * Introduced single thread validation function.
> * Removed pkt_stream_invalid().
> * Updated TEST_TYPE_POLL_TXQ_FULL testcase to create invalid frame.
> * Removed timer from send_pkts().
> * Removed boolean variable skip_rx and skip_tx.
> Change in v4:
> * Added is_umem_valid()
for single patches, I believe that it's concerned a better practice to
include the versioning below the '---' line?
>
> Signed-off-by: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
> ---
> tools/testing/selftests/bpf/xskxceiver.c | 166 +++++++++++++++++------
> tools/testing/selftests/bpf/xskxceiver.h | 8 +-
> 2 files changed, 134 insertions(+), 40 deletions(-)
>
I don't think these grammar suggestions require a new revision, so:
Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
next prev parent reply other threads:[~2022-08-10 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 14:43 [PATCH bpf-next v4] selftests: xsk: Update poll test cases Shibin Koikkara Reeny
2022-08-10 13:08 ` Maciej Fijalkowski [this message]
2022-08-10 15:17 ` Daniel Borkmann
2022-08-11 14:45 ` Koikkara Reeny, Shibin
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=YvOtvgdSnOhUd9Po@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ciara.loftus@intel.com \
--cc=daniel@iogearbox.net \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shibin.koikkara.reeny@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 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.