From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/3] selftests/net: various
Date: Thu, 31 May 2018 12:14:37 -0400 [thread overview]
Message-ID: <20180531161440.89709-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
A few odds and ends to network tests:
- msg_zerocopy: run as part of kselftest
- udp gso: add missing bounds test for minimal sizes
- psocket_snd: initial basic conformance test
Willem de Bruijn (3):
selftests/net: enable msg_zerocopy test
selftests/net: udpgso: test small gso_size boundary conditions
selftests/net: add packet socket packet_snd test
tools/testing/selftests/net/.gitignore | 1 +
tools/testing/selftests/net/Makefile | 4 +-
tools/testing/selftests/net/msg_zerocopy.sh | 8 +
tools/testing/selftests/net/psock_snd.c | 398 ++++++++++++++++++++
tools/testing/selftests/net/psock_snd.sh | 98 +++++
tools/testing/selftests/net/udpgso.c | 77 +++-
6 files changed, 582 insertions(+), 4 deletions(-)
create mode 100644 tools/testing/selftests/net/psock_snd.c
create mode 100755 tools/testing/selftests/net/psock_snd.sh
--
2.17.0.921.gf22659ad46-goog
next reply other threads:[~2018-05-31 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 16:14 Willem de Bruijn [this message]
2018-05-31 16:14 ` [PATCH net-next 1/3] selftests/net: enable msg_zerocopy test Willem de Bruijn
2018-05-31 16:14 ` [PATCH net-next 2/3] selftests/net: udpgso: test small gso_size boundary conditions Willem de Bruijn
2018-05-31 16:14 ` [PATCH net-next 3/3] selftests/net: add packet socket packet_snd test Willem de Bruijn
2018-06-04 13:50 ` [PATCH net-next 0/3] selftests/net: various David Miller
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=20180531161440.89709-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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).