On Thu, 11 Aug 2022 09:18:03 -0700 sdf@xxxxxxxxxx wrote:
> > +attr-cnt-suffix: CNT
>
> Is it a hack to make the generated header fit into existing
> implementation?
Yup.
> Should we #define ETHTOOL_XXX_CNT ETHTOOL_XXX in
> the implementation instead? (or s/ETHTOOL_XXX_CNT/ETHTOOL_XXX/ the
> source itself?)
We could, I guess. To be clear this controls the count, IOW:
enum {
PREFIX_A_BLA_ATTR = 1,
PREFIX_A_ANOTHER_ATTR,
PREFIX_A_AND_ONEMORE,
__PFREIX_A_CNT, // <--- This thing
};
#define PREFIX_A_MAX (__PFREIX_A_CNT - 1)
It's not used in the generated code, only if we codegen the uAPI,
AFAIR. So we'd need a way to tell the generator of the uAPI about
the situation, anyway. I could be misremembering.
> > +attribute-spaces:
>
> Are you open to bike shedding? :-)
I can't make promises that I'll change things but I'm curious
to hear it!
> I like how ethtool_netlink.h calls these 'message types'.
It calls operation types message types, not attr spaces.
I used ops because that's what genetlink calls things.
> > + -
> > + name: header
> > + name-prefix: ETHTOOL_A_HEADER_
>
> Any issue with name-prefix+name-suffix being non-greppable? Have you tried
> something like this instead:
>
> - name: ETHTOOL_A_HEADER # this is fake, for ynl reference only
> attributes:
> - name: ETHTOOL_A_HEADER_DEV_INDEX
> val:
> type:
> - name ETHTOOL_A_HEADER_DEV_NAME
> ..
>
> It seems a bit easier to map the spec into what it's going to produce.
> For example, it took me a while to translate 'channels_get' below into
> ETHTOOL_MSG_CHANNELS_GET.
>
> Or is it too much ETHTOOL_A_HEADER_?
Dunno, that'd mean that the Python method is called
ETHTOOL_MSG_CHANNELS_GET rather than just channels_get.
I don't want to force all languages to use the C naming.
The C naming just leads to silly copy'n'paste issues like
f329a0ebeab.
> > + len: ALTIFNAMSIZ - 1
>
> Not sure how strict you want to be here. ALTIFNAMSIZ is defined
> somewhere else it seems? (IOW, do we want to have implicit dependencies
> on external/uapi headers?)
Good catch, I'm aware. I was planning to add a "header constants"
section or some such. A section in "headers" which defines the
constants which C code will get from the headers.
For Python it does not matter, as we don't have to size arrays.
I was wondering if it will matter for other languages, like Rust?
> > + - header
> > + - rx_count
> > + - tx_count
> > + - other_count
> > + - combined_count
>
> My netlink is super rusty, might be worth mentioning in the spec: these
> are possible attributes, but are all of them required?
Right, will do, nothing is required, or rather requirements are kinda
hard to express and checked by the code in the kernel.
> You also mention the validation part in the cover letter, do you plan
> add some of these policy properties to the spec or everything is
> there already? (I'm assuming we care about the types which we have above and
> optional/required attribute indication?)
Yeah, my initial plan was to encode requirement in the policy but its
not trivial. So I left it as future extension. Besides things which are
required today may not be tomorrow, so its a bit of a strange thing.
Regarding policy properties I'm intending to support all of the stuff
that the kernel policies recognize... but somehow most families I
converted don't have validation (only mask and length :S).
Actually for DPLL I have a nice validation trick. You can define an
enum:
constants:
-
type: flags
name: genl_get_flags
value-prefix: DPLL_FLAG_
values: [ sources, outputs, status ]
Then for an attribute you link it:
-
name: flags
type: u32
flags-mask: genl_get_flags
And that will auto an enum:
enum dpll_genl_get_flags {
DPLL_FLAG_SOURCES = 1,
DPLL_FLAG_OUTPUTS = 2,
DPLL_FLAG_STATUS = 4,
};
And a policy with a mask:
[DPLLA_FLAGS] = NLA_POLICY_MASK(NLA_U32, 0x7),
