All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
To: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	John Fastabend <john.fastabend@gmail.com>
Cc: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>,
	"David S . Miller" <davem@davemloft.net>,
	Shuah Khan <shuah@kernel.org>,
	netdev@vger.kernel.org
Subject: [PATCH bpf-next 0/5] fix test_sockmap
Date: Fri, 18 May 2018 16:17:48 +0900	[thread overview]
Message-ID: <20180518071753.4768-1-bhole_prashant_q7@lab.ntt.co.jp> (raw)

This series fixes bugs in test_sockmap code. They weren't caught
previously because failure in RX/TX thread was not notified to the
main thread.

Also fixed data verification logic and slightly improved test output
such that parameters values (cork, apply, start, end) of failed test
can be easily seen.

Note: Even after fixing above problems there are issues with tests
which set cork parameter. Tests fail (RX thread timeout) when cork
value is non-zero and overall data sent by TX thread isn't multiples
of cork value.

Prashant Bhole (5):
  selftests/bpf: test_sockmap, check test failure
  selftests/bpf: test_sockmap, join cgroup in selftest mode
  selftests/bpf: test_sockmap, fix test timeout
  selftests/bpf: test_sockmap, fix data verification
  selftests/bpf: test_sockmap, print additional test options

 tools/testing/selftests/bpf/test_sockmap.c | 76 +++++++++++++++++++++++-------
 1 file changed, 58 insertions(+), 18 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-05-18  7:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  7:17 Prashant Bhole [this message]
2018-05-18  7:17 ` [PATCH bpf-next 1/5] selftests/bpf: test_sockmap, check test failure Prashant Bhole
2018-05-18  7:17 ` [PATCH bpf-next 2/5] selftests/bpf: test_sockmap, join cgroup in selftest mode Prashant Bhole
2018-05-18 16:45   ` John Fastabend
2018-05-21  5:15     ` Prashant Bhole
2018-05-21 17:10       ` John Fastabend
2018-05-18  7:17 ` [PATCH bpf-next 3/5] selftests/bpf: test_sockmap, fix test timeout Prashant Bhole
2018-05-18 16:47   ` John Fastabend
2018-05-21  5:15     ` Prashant Bhole
2018-05-21 17:13       ` John Fastabend
2018-05-18  7:17 ` [PATCH bpf-next 4/5] selftests/bpf: test_sockmap, fix data verification Prashant Bhole
2018-05-18 16:49   ` John Fastabend
2018-05-18  7:17 ` [PATCH bpf-next 5/5] selftests/bpf: test_sockmap, print additional test options Prashant Bhole
2018-05-18 16:51   ` John Fastabend
2018-05-18 16:42 ` [PATCH bpf-next 0/5] fix test_sockmap John Fastabend
2018-05-21  5:13   ` Prashant Bhole
2018-05-21 17:08     ` John Fastabend
2018-05-23  9:44       ` Prashant Bhole
2018-05-24  4:47         ` Prashant Bhole
2018-05-24  4:58           ` John Fastabend
2018-05-25  8:28             ` Prashant Bhole
2018-05-25 14:01               ` John Fastabend
2018-05-28  4:16                 ` Prashant Bhole
2018-05-18 16:54 ` Shuah Khan
2018-05-18 16:54   ` Shuah Khan
2018-05-18 16:54   ` shuah
2018-05-18 17:23   ` Daniel Borkmann
2018-05-18 17:23     ` Daniel Borkmann
2018-05-18 17:23     ` daniel
2018-05-21  5:16   ` Prashant Bhole
2018-05-21  5:16     ` Prashant Bhole
2018-05-21  5:16     ` bhole_prashant_q7

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=20180518071753.4768-1-bhole_prashant_q7@lab.ntt.co.jp \
    --to=bhole_prashant_q7@lab.ntt.co.jp \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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 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.