From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, ncardwell@google.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, matttbe@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next v2 0/3] selftests/net: packetdrill: netns and two imports
Date: Wed, 11 Sep 2024 20:52:39 -0400 [thread overview]
Message-ID: <20240912005317.1253001-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
1/3: run in nets, as discussed, and add missing CONFIGs
2/3: import tcp/zerocopy
3/3: import tcp/slow_start
Willem de Bruijn (3):
selftests/net: packetdrill: run in netns and expand config
selftests/net: packetdrill: import tcp/zerocopy
selftests/net: packetdrill: import tcp/slow_start
.../selftests/net/packetdrill/Makefile | 1 +
.../testing/selftests/net/packetdrill/config | 6 +
.../selftests/net/packetdrill/ksft_runner.sh | 4 +-
.../selftests/net/packetdrill/set_sysctls.py | 38 ++++++
...tcp_slow_start_slow-start-ack-per-1pkt.pkt | 56 +++++++++
...tart_slow-start-ack-per-2pkt-send-5pkt.pkt | 33 +++++
...tart_slow-start-ack-per-2pkt-send-6pkt.pkt | 34 +++++
...tcp_slow_start_slow-start-ack-per-2pkt.pkt | 42 +++++++
...tcp_slow_start_slow-start-ack-per-4pkt.pkt | 35 ++++++
.../tcp_slow_start_slow-start-after-idle.pkt | 39 ++++++
...slow_start_slow-start-after-win-update.pkt | 50 ++++++++
...t_slow-start-app-limited-9-packets-out.pkt | 38 ++++++
.../tcp_slow_start_slow-start-app-limited.pkt | 36 ++++++
..._slow_start_slow-start-fq-ack-per-2pkt.pkt | 63 ++++++++++
.../net/packetdrill/tcp_zerocopy_basic.pkt | 55 ++++++++
.../net/packetdrill/tcp_zerocopy_batch.pkt | 41 ++++++
.../net/packetdrill/tcp_zerocopy_client.pkt | 30 +++++
.../net/packetdrill/tcp_zerocopy_closed.pkt | 44 +++++++
.../packetdrill/tcp_zerocopy_epoll_edge.pkt | 61 +++++++++
.../tcp_zerocopy_epoll_exclusive.pkt | 63 ++++++++++
.../tcp_zerocopy_epoll_oneshot.pkt | 66 ++++++++++
.../tcp_zerocopy_fastopen-client.pkt | 56 +++++++++
.../tcp_zerocopy_fastopen-server.pkt | 44 +++++++
.../net/packetdrill/tcp_zerocopy_maxfrags.pkt | 118 ++++++++++++++++++
.../net/packetdrill/tcp_zerocopy_small.pkt | 57 +++++++++
25 files changed, 1108 insertions(+), 2 deletions(-)
create mode 100755 tools/testing/selftests/net/packetdrill/set_sysctls.py
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-ack-per-1pkt.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-ack-per-2pkt-send-5pkt.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-ack-per-2pkt-send-6pkt.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-ack-per-2pkt.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-ack-per-4pkt.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-after-idle.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-after-win-update.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-app-limited-9-packets-out.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-app-limited.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_slow_start_slow-start-fq-ack-per-2pkt.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_basic.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_batch.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_client.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_closed.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_epoll_edge.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_epoll_exclusive.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_epoll_oneshot.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_fastopen-client.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_fastopen-server.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_maxfrags.pkt
create mode 100644 tools/testing/selftests/net/packetdrill/tcp_zerocopy_small.pkt
--
2.46.0.598.g6f2099f65c-goog
next reply other threads:[~2024-09-12 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 0:52 Willem de Bruijn [this message]
2024-09-12 0:52 ` [PATCH net-next v2 1/3] selftests/net: packetdrill: run in netns and expand config Willem de Bruijn
2024-09-12 0:52 ` [PATCH net-next v2 2/3] selftests/net: packetdrill: import tcp/zerocopy Willem de Bruijn
2024-09-12 0:52 ` [PATCH net-next v2 3/3] selftests/net: packetdrill: import tcp/slow_start Willem de Bruijn
2024-09-12 11:22 ` [PATCH net-next v2 0/3] selftests/net: packetdrill: netns and two imports Matthieu Baerts
2024-09-12 12:10 ` Willem de Bruijn
2024-09-16 16:48 ` Stanislav Fomichev
2024-09-16 20:54 ` Willem de Bruijn
2024-09-13 2:20 ` patchwork-bot+netdevbpf
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=20240912005317.1253001-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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