[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2plh0r3zn.fsf@gmail.com>
Date: Fri, 25 Apr 2025 10:21:16 +0100
From: Donald Hunter <donald.hunter@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
jacob.e.keller@...el.com, sdf@...ichev.me, jdamato@...tly.com
Subject: Re: [PATCH net-next v2 06/12] tools: ynl-gen: support CRUD-like
notifications for classic Netlink
Jakub Kicinski <kuba@...nel.org> writes:
> Allow CRUD-style notification where the notification is more
> like the response to the request, which can optionally be
> looped back onto the requesting socket. Since the notification
> and request are different ops in the spec, for example:
>
> -
> name: delrule
> doc: Remove an existing FIB rule
> attribute-set: fib-rule-attrs
> do:
> request:
> value: 33
> attributes: *fib-rule-all
> -
> name: delrule-ntf
> doc: Notify a rule deletion
> value: 33
> notify: getrule
>
> We need to find the request by ID. Ideally we'd detect this model
> from the spec properties, rather than assume that its what all
> classic netlink families do. But maybe that'd cause this model
> to spread and its easy to get wrong. For now assume CRUD == classic.
>
> Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Reviewed-by: Donald Hunter <donald.hunter@...il.com>
Powered by blists - more mailing lists