Re: [PATCH net-next v1 02/12] tools/net/ynl: Support sub-messages in nested attribute spaces
From: Jacob Keller <jacob.e.keller@intel.com>
Date: 2024-02-02 17:12:19
Also in:
linux-doc
On 2/1/2024 4:04 PM, Jakub Kicinski wrote:
On Thu, 1 Feb 2024 12:53:08 -0800 Jacob Keller wrote:quoted
On 1/29/2024 5:42 PM, Jakub Kicinski wrote:quoted
Whether YNL specs should replace policy dumps completely (by building the YAML into the kernel, and exposing via sysfs like kheaders or btf) - I'm not sure. I think I used policy dumps twice in my life. They are not all that useful, IMVHO...Many older genetlink/netlink families don't have a super robust or specific policy. For example, devlink has a single enum for all attributes, and the policy is not specified per command. The policy simply accepts all attributes for every command. This means that you can't rely on policy to decide whether an attribute has meaning for a given command.FWIW Jiri converted devlink to use ynl policy generation. AFAIU it now only accepts what's used and nobody complained, yet, knock wood.
Oh, I guess I missed that. That's awesome.
Agreed on other points :)