Netdev List
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org,  davem@davemloft.net,
	 echaudro@redhat.com, edumazet@google.com,  horms@kernel.org,
	 i.maximets@ovn.org, kuba@kernel.org,  pabeni@redhat.com,
	 shuah@kernel.org, dev@openvswitch.org,
	 linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3] selftests: openvswitch: add dec_ttl action support and test
Date: Thu, 28 May 2026 08:15:52 -0400	[thread overview]
Message-ID: <f7ttsrrpw5j.fsf@redhat.com> (raw)
In-Reply-To: <20260527080601.615607-1-houminxi@gmail.com> (Minxi Hou's message of "Wed, 27 May 2026 16:06:01 +0800")

Minxi Hou <houminxi@gmail.com> writes:

> Add dec_ttl action support to the OVS kernel datapath selftest
> framework:
>
>   - Add dec_ttl nested NLA class to ovs-dpctl.py with proper
>     OVS_DEC_TTL_ATTR_ACTION sub-attribute handling
>   - Add parse support for dec_ttl(le_1(<inner_actions>)) action
>     string, consistent with the odp-util.c format where le_1()
>     holds the actions taken when TTL reaches 1
>   - Add dpstr output formatting for dec_ttl actions
>   - Add test_dec_ttl() to openvswitch.sh that verifies:
>     * Normal TTL packets are forwarded after decrement
>     * TTL=1 packets are dropped (TTL expiry)
>     * Graceful skip via ksft_skip if kernel lacks dec_ttl support
>
> The dec_ttl class uses late-binding type resolution to reference
> ovsactions for its inner action list, avoiding circular references
> at class definition time.
>
> Signed-off-by: Minxi Hou <houminxi@gmail.com>
> ---

Thanks Minxi - this case will be very helpful.

Reviewed-by: Aaron Conole <aconole@redhat.com>


      reply	other threads:[~2026-05-28 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27  8:06 [PATCH net-next v3] selftests: openvswitch: add dec_ttl action support and test Minxi Hou
2026-05-28 12:15 ` Aaron Conole [this message]

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=f7ttsrrpw5j.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=houminxi@gmail.com \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox