From: Donald Hunter <donald.hunter@gmail.com>
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, aconole@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] netlink: specs: add OVS packet family specification
Date: Tue, 19 May 2026 10:44:03 +0100 [thread overview]
Message-ID: <m233znvin0.fsf@gmail.com> (raw)
In-Reply-To: <20260518164029.439928-2-houminxi@gmail.com>
Minxi Hou <houminxi@gmail.com> writes:
> Add YAML netlink spec for the OVS_PACKET_FAMILY (ovs_packet).
> This completes the set of OVS genetlink family specs (ovs_datapath,
> ovs_flow, ovs_vport already exist).
>
> The spec defines three operations: MISS (event), ACTION (event),
> and EXECUTE (do). MISS and ACTION are kernel-to-userspace upcalls
> sent via genlmsg_unicast(); EXECUTE is the only registered genl
> operation.
>
> Key, actions, and egress-tun-key attributes are typed as binary
> rather than nest because the nested attribute definitions belong
> to the ovs_flow spec and cross-spec references are not supported
> by the YNL framework.
>
> Signed-off-by: Minxi Hou <houminxi@gmail.com>
Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
next prev parent reply other threads:[~2026-05-19 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 16:40 [PATCH v2 0/2] Add OVS packet family YNL spec and unicast notification support Minxi Hou
2026-05-18 16:40 ` [PATCH v2 1/2] netlink: specs: add OVS packet family specification Minxi Hou
2026-05-19 9:44 ` Donald Hunter [this message]
2026-05-18 16:40 ` [PATCH v2 2/2] tools: ynl: add unicast notification receive support Minxi Hou
2026-05-19 9:44 ` Donald Hunter
2026-05-19 9:50 ` 侯敏熙
2026-05-19 10:20 ` Donald Hunter
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=m233znvin0.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=houminxi@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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