[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230801105726.1af6a7e1@kernel.org>
Date: Tue, 1 Aug 2023 10:57:26 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Leon Romanovsky <leon@...nel.org>
Cc: Lin Ma <linma@....edu.cn>, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, fw@...len.de,
yang.lee@...ux.alibaba.com, jgg@...pe.ca, markzhang@...dia.com,
phaddad@...dia.com, yuancan@...wei.com, ohartoov@...dia.com,
chenzhongjin@...wei.com, aharonl@...dia.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH net v1 1/2] netlink: let len field used to parse
type-not-care nested attrs
On Tue, 1 Aug 2023 11:11:17 +0300 Leon Romanovsky wrote:
> IMHO, you are lowering too much the separation line between simple vs.
> advanced use cases.
>
> I had no idea that my use-case of passing nested netlink array is counted
> as advanced usage.
Agreed, that's a fair point. I'm guessing it was inspired by the
ethtool stats? (Which in hindsight were a mistake on my part.)
For the longest time there was no docs or best practices for netlink.
We have the documentation and more infrastructure in place now.
I hope if you wrote the code today the distinction would have been
clearer.
If we start adding APIs for various one-(two?)-offs from the past
we'll never dig ourselves out of the "no idea what's the normal use
of these APIs" hole..
Powered by blists - more mailing lists