netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davide Caratti <dcaratti@redhat.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>, Ilya Maximets <i.maximets@ovn.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, Pedro Tammela <pctammela@mojatatu.com>
Subject: [PATCH net-next v4 0/4] net/sched: act_tunnel_key: add support for TUNNEL_DONT_FRAGMENT
Date: Wed, 29 Mar 2023 11:54:51 +0200	[thread overview]
Message-ID: <cover.1680082990.git.dcaratti@redhat.com> (raw)

- patch 1 extends TC tunnel_key action to add support for TUNNEL_DONT_FRAGMENT 
- patch 2 extends tdc to skip tests when iproute2 support is missing
- patch 3 adds a tdc test case to verify functionality of the control plane
- patch 4 adds a net/forwarding test case to verify functionality of the data plane

v3->v4:
 - remove misleading "failure" wording in the printout (thanks to Pedro
   Tammela)
 - fix permissions (+x) of net/forwarding kselftest 

v2->v3:
 - introduce new "dependsOn" property instead of extending "skip"
   (suggested by Pedro Tammela)
 - fix wrong indentation (thanks to Jakub Kicinski)

v1->v2:
 - split patchset to have test cases in separate patches (thanks to
   Pedro Tammela)
 - change TCA_TUNNEL_KEY_NO_FRAG attribute, so that it is a flag istead
   of u8 (thanks to Jakub Kicinski)
 - add missing TEST_PROGS assignment (thanks to Jakub Kicinski)

Davide Caratti (4):
  net/sched: act_tunnel_key: add support for "don't fragment"
  selftests: tc-testing: add "depends_on" property to skip tests
  selftests: tc-testing: add tunnel_key "nofrag" test case
  selftests: forwarding: add tunnel_key "nofrag" test case

 include/uapi/linux/tc_act/tc_tunnel_key.h     |   1 +
 net/sched/act_tunnel_key.c                    |   5 +
 .../testing/selftests/net/forwarding/Makefile |   1 +
 .../selftests/net/forwarding/tc_tunnel_key.sh | 161 ++++++++++++++++++
 .../creating-testcases/AddingTestCases.txt    |   2 +
 .../tc-tests/actions/tunnel_key.json          |  25 +++
 tools/testing/selftests/tc-testing/tdc.py     |  13 ++
 7 files changed, 208 insertions(+)
 create mode 100755 tools/testing/selftests/net/forwarding/tc_tunnel_key.sh

-- 
2.39.2


             reply	other threads:[~2023-03-29  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  9:54 Davide Caratti [this message]
2023-03-29  9:54 ` [PATCH net-next v4 1/4] net/sched: act_tunnel_key: add support for "don't fragment" Davide Caratti
2023-03-29  9:54 ` [PATCH net-next v4 2/4] selftests: tc-testing: add "depends_on" property to skip tests Davide Caratti
2023-03-29  9:54 ` [PATCH net-next v4 3/4] selftests: tc-testing: add tunnel_key "nofrag" test case Davide Caratti
2023-03-29  9:54 ` [PATCH net-next v4 4/4] selftests: forwarding: " Davide Caratti
2023-03-31  6:30 ` [PATCH net-next v4 0/4] net/sched: act_tunnel_key: add support for TUNNEL_DONT_FRAGMENT 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=cover.1680082990.git.dcaratti@redhat.com \
    --to=dcaratti@redhat.com \
    --cc=i.maximets@ovn.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pctammela@mojatatu.com \
    --cc=xiyou.wangcong@gmail.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).