netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail.com>
To: "Chia-Yu Chang (Nokia)" <chia-yu.chang@nokia-bell-labs.com>
Cc: "xandfury@gmail.com" <xandfury@gmail.com>,
	 "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	 "dave.taht@gmail.com" <dave.taht@gmail.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	 "jhs@mojatatu.com" <jhs@mojatatu.com>,
	 "kuba@kernel.org" <kuba@kernel.org>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
	"jiri@resnulli.us" <jiri@resnulli.us>,
	 "davem@davemloft.net" <davem@davemloft.net>,
	 "edumazet@google.com" <edumazet@google.com>,
	"horms@kernel.org" <horms@kernel.org>,
	 "andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	 "ast@fiberby.net" <ast@fiberby.net>,
	"liuhangbin@gmail.com" <liuhangbin@gmail.com>,
	 "shuah@kernel.org" <shuah@kernel.org>,
	 "linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	 "ij@kernel.org" <ij@kernel.org>,
	"ncardwell@google.com" <ncardwell@google.com>,
	 "Koen De Schepper (Nokia)"
	<koen.de_schepper@nokia-bell-labs.com>,
	 g.white <g.white@cablelabs.com>,
	 "ingemar.s.johansson@ericsson.com"
	<ingemar.s.johansson@ericsson.com>,
	 "mirja.kuehlewind@ericsson.com" <mirja.kuehlewind@ericsson.com>,
	 "cheshire@apple.com" <cheshire@apple.com>,
	 "rs.ietf@gmx.at" <rs.ietf@gmx.at>,
	"Jason_Livingood@comcast.com" <Jason_Livingood@comcast.com>,
	 vidhi_goel <vidhi_goel@apple.com>
Subject: Re: [PATCH v12 net-next 1/5] Documentation: netlink: specs: tc: Add DualPI2 specification
Date: Thu, 24 Apr 2025 10:26:15 +0100	[thread overview]
Message-ID: <m2wmb9syfc.fsf@gmail.com> (raw)
In-Reply-To: <PAXPR07MB79840FF6B073C61136AC238CA3BA2@PAXPR07MB7984.eurprd07.prod.outlook.com> (Chia-Yu Chang's message of "Wed, 23 Apr 2025 17:15:15 +0000")

"Chia-Yu Chang (Nokia)" <chia-yu.chang@nokia-bell-labs.com> writes:

>> The syntax is not valid so this doesn't pass the schema check and presumably hasn't been tested. Please validate YNL .yaml additions e.g.
>> 
>> ./tools/net/ynl/pyynl/cli.py \
>>     --spec Documentation/netlink/specs/tc.yaml \
>>     --list-ops
>> 
>> ...
>> jsonschema.exceptions.ValidationError: Additional properties are not allowed ('entries' was unexpected) ...
>> On instance['attribute-sets'][30]['attributes'][14]:
>>     {'name': 'gso_split',
>>      'type': 'flags',
>>      'doc': 'Split aggregated skb or not',
>>      'entries': ['split_gso', 'no_split_gso']}
>> 
>
> Hi Donald,
>
> 	Thanks for the feedback, and I will take actions for below points as well as the corresponding iproute2-net fixes.
> 	One more question is I see "uint" type is not valid during validation - see below (but which was suggested in v11), shall I change it back to u32/u8?
>
> Failed validating 'enum' in schema['properties']['definitions']['items']['properties']['members']['items']['properties']['type']:
>     {'description': "The netlink attribute type. Members of type 'binary' "
>                     "or 'pad'\n"
>                     "must also have the 'len' property set.\n",
>      'enum': ['u8',
>               'u16',
>               'u32',
>               'u64',
>               's8',
>               's16',
>               's32',
>               's64',
>               'string',
>               'binary',
>               'pad']}
>
> On instance['definitions'][42]['members'][12]['type']:
>     'uint'	

The advice from Paolo was a bit misleading. It is correct for netlink
attributes which support variable size scalars, but not for struct
members which must be a fixed size.

So for tc-dualpi2-xstats, the member types must match the struct
tc_dualpi2_xstats types.

  reply	other threads:[~2025-04-24 10:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 20:15 [PATCH v12 net-next 0/5] DUALPI2 patch chia-yu.chang
2025-04-22 20:15 ` [PATCH v12 net-next 1/5] Documentation: netlink: specs: tc: Add DualPI2 specification chia-yu.chang
2025-04-23 11:29   ` Donald Hunter
2025-04-23 17:15     ` Chia-Yu Chang (Nokia)
2025-04-24  9:26       ` Donald Hunter [this message]
2025-04-22 20:15 ` [PATCH v12 net-next 2/5] selftests/tc-testing: Add selftests for qdisc DualPI2 chia-yu.chang
2025-04-22 20:16 ` [PATCH v12 net-next 3/5] sched: Struct definition and parsing of dualpi2 qdisc chia-yu.chang
2025-04-23 12:03   ` Donald Hunter
2025-04-25 21:17     ` Chia-Yu Chang (Nokia)
2025-04-22 20:16 ` [PATCH v12 net-next 4/5] sched: Dump configuration and statistics " chia-yu.chang
2025-04-22 20:16 ` [PATCH v12 net-next 5/5] sched: Add enqueue/dequeue " chia-yu.chang

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=m2wmb9syfc.fsf@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=Jason_Livingood@comcast.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@fiberby.net \
    --cc=cheshire@apple.com \
    --cc=chia-yu.chang@nokia-bell-labs.com \
    --cc=dave.taht@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=g.white@cablelabs.com \
    --cc=horms@kernel.org \
    --cc=ij@kernel.org \
    --cc=ingemar.s.johansson@ericsson.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=koen.de_schepper@nokia-bell-labs.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=mirja.kuehlewind@ericsson.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rs.ietf@gmx.at \
    --cc=shuah@kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=vidhi_goel@apple.com \
    --cc=xandfury@gmail.com \
    --cc=xiyou.wangcong@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).