From: Donald Hunter <donald.hunter@gmail.com>
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Aaron Conole <aconole@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] netlink: specs: add OVS packet family specification
Date: Mon, 18 May 2026 14:52:10 +0100 [thread overview]
Message-ID: <m2jyt0vn91.fsf@gmail.com> (raw)
In-Reply-To: <20260517083358.2088599-2-houminxi@gmail.com>
Minxi Hou <houminxi@gmail.com> writes:
> +operations:
> + fixed-header: ovs-header
> + name-prefix: ovs-packet-cmd-
> + list:
> + -
> + name: miss
> + doc: Notify userspace of a flow table miss for a received packet.
> + value: 1
> + attribute-set: packet
> + event:
> + attributes:
Instead of repeating the same attributes, this attribute list could be
declared with an anchor name such as &event-attrs which could be
referenced in the action event. E.g.
attributes: &event-attrs
> + - packet
> + - key
> + - userdata
> + - actions
> + - egress-tun-key
> + - mru
> + - len
> + - hash
> + -
> + name: action
> + doc: Notify userspace as requested by an OVS_ACTION_ATTR_USERSPACE action.
> + value: 2
> + attribute-set: packet
> + event:
> + attributes:
attributes: *event-attrs
> + - packet
> + - key
> + - userdata
> + - actions
> + - egress-tun-key
> + - mru
> + - len
> + - hash
Otherwise looks good to me, thanks.
next prev parent reply other threads:[~2026-05-18 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 8:33 [PATCH net-next 0/2] netlink: specs: complete OVS family coverage Minxi Hou
2026-05-17 8:33 ` [PATCH 1/2] netlink: specs: add OVS packet family specification Minxi Hou
2026-05-18 13:52 ` Donald Hunter [this message]
2026-05-17 8:33 ` [PATCH 2/2] tools: ynl: add unicast notification receive support Minxi Hou
2026-05-18 13:56 ` Donald Hunter
2026-05-17 8:55 ` [PATCH net-next 0/2] netlink: specs: complete OVS family coverage Minxi Hou
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=m2jyt0vn91.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