From: Jakub Kicinski <kuba@kernel.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: Adrian Moreno <amorenoz@redhat.com>,
netdev@vger.kernel.org, jiri@resnulli.us,
xiyou.wangcong@gmail.com, cmi@nvidia.com, yotam.gi@gmail.com,
aconole@redhat.com, echaudro@redhat.com, horms@kernel.org
Subject: Re: [RFC net-next v2 5/5] net:openvswitch: add psample support
Date: Tue, 9 Apr 2024 14:49:47 -0700 [thread overview]
Message-ID: <20240409144947.1379e33b@kernel.org> (raw)
In-Reply-To: <f2bbefed-f17c-4127-a87b-13a5933e98cd@ovn.org>
On Tue, 9 Apr 2024 11:35:04 +0200 Ilya Maximets wrote:
> > If we try to implement all our actions following this way, and we keep just
> > copying the incoming actions into the internal representation, we incur in
> > unnecessary memory overhead (e.g: storing 2x struct nlaattr + padding of extra
> > memory to store 2 integers).
> >
> > I don't want to derail the discussion into historical or futuristic changes,
> > just saying that the approach taken in the SAMPLE action (not including this
> > patch) of exposing arguments as attributes but having a kernel-only struct to
> > store them seems to me a good compromise.
>
> Sure. As I said, it's fine to have internal structures. My comment
> was mainly about uAPI part. We should avoid structures in uAPI if
> possible, as they are very hard to maintain and keep compatible with
> older userspace in case some changes will be needed in the future.
FWIW there are some YAML specs for ovs under
Documentation/netlink/specs/ovs_*
perhaps they should also be updated?
next prev parent reply other threads:[~2024-04-09 21:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 12:57 [RFC net-next v2 0/5] net: openvswitch: Add sample multicasting Adrian Moreno
2024-04-08 12:57 ` [RFC net-next v2 1/5] net: netlink: export genl private pointer getters Adrian Moreno
2024-04-09 21:48 ` Jakub Kicinski
2024-04-08 12:57 ` [RFC net-next v2 2/5] net: psample: add multicast filtering on group_id Adrian Moreno
2024-04-08 13:18 ` Ilya Maximets
2024-04-08 19:24 ` Adrian Moreno
2024-04-09 14:43 ` Aaron Conole
2024-04-10 13:32 ` Adrian Moreno
2024-04-10 13:06 ` Ido Schimmel
2024-04-10 13:42 ` Adrian Moreno
2024-04-08 12:57 ` [RFC net-next v2 3/5] net: psample: add user cookie Adrian Moreno
2024-04-08 13:19 ` Ilya Maximets
2024-04-08 19:28 ` Adrian Moreno
2024-04-08 20:28 ` Ilya Maximets
2024-04-08 12:57 ` [RFC net-next v2 4/5] net:sched:act_sample: add action cookie to sample Adrian Moreno
2024-04-08 13:20 ` Ilya Maximets
2024-04-11 8:40 ` Adrian Moreno
2024-04-08 12:57 ` [RFC net-next v2 5/5] net:openvswitch: add psample support Adrian Moreno
2024-04-08 13:37 ` Ilya Maximets
2024-04-08 19:48 ` Adrian Moreno
2024-04-08 20:40 ` Ilya Maximets
2024-04-09 8:16 ` Adrian Moreno
2024-04-09 9:35 ` Ilya Maximets
2024-04-09 21:49 ` Jakub Kicinski [this message]
2024-04-10 13:44 ` Adrian Moreno
2024-04-08 13:16 ` [RFC net-next v2 0/5] net: openvswitch: Add sample multicasting Ilya Maximets
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=20240409144947.1379e33b@kernel.org \
--to=kuba@kernel.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=cmi@nvidia.com \
--cc=echaudro@redhat.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yotam.gi@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).