[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220818201345.7b523818@kernel.org>
Date: Thu, 18 Aug 2022 20:13:45 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Stanislav Fomichev <sdf@...gle.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, corbet@....net,
johannes@...solutions.net, stephen@...workplumber.org,
ecree.xilinx@...il.com, benjamin.poirier@...il.com,
idosch@...sch.org, f.fainelli@...il.com, jiri@...nulli.us,
dsahern@...nel.org, fw@...len.de, linux-doc@...r.kernel.org,
jhs@...atatu.com, tgraf@...g.ch, jacob.e.keller@...el.com,
svinota.saveliev@...il.com
Subject: Re: [PATCH net-next 2/2] docs: netlink: basic introduction to
Netlink
On Wed, 17 Aug 2022 21:05:21 -0700 Stanislav Fomichev wrote:
> > +Most of the concepts and examples here refer to the ``NETLINK_ROUTE`` family,
> > +which covers much of the configuration of the Linux networking stack.
> > +Real documentation of that family, deserves a chapter (or a book) of its own.
>
> I'm assuming the answer is "no", but nonetheless: is it possible to
> use classic families over generic netlink (discover/get policy/etc)?
Not as far as I know.
> So we can just assume everything is genetlink and safely ignore all
> old quirks of the classic variant?
The behavior may differ a little with older families when it comes to
validation but yes, for the most part genetlink users should be able
to ignore all the quirks.
Powered by blists - more mailing lists