[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO1PR11MB5089F2051CB169BE94370A42D66D9@CO1PR11MB5089.namprd11.prod.outlook.com>
Date: Thu, 18 Aug 2022 21:26:29 +0000
From: "Keller, Jacob E" <jacob.e.keller@...el.com>
To: Jakub Kicinski <kuba@...nel.org>,
Edward Cree <ecree.xilinx@...il.com>
CC: Stephen Hemminger <stephen@...workplumber.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"sdf@...gle.com" <sdf@...gle.com>, "vadfed@...com" <vadfed@...com>,
"johannes@...solutions.net" <johannes@...solutions.net>,
"jiri@...nulli.us" <jiri@...nulli.us>,
"dsahern@...nel.org" <dsahern@...nel.org>,
"fw@...len.de" <fw@...len.de>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: RE: [RFC net-next 3/4] ynl: add a sample python library
> -----Original Message-----
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Friday, August 12, 2022 4:08 PM
> To: Edward Cree <ecree.xilinx@...il.com>
> Cc: Stephen Hemminger <stephen@...workplumber.org>;
> netdev@...r.kernel.org; davem@...emloft.net; edumazet@...gle.com;
> pabeni@...hat.com; sdf@...gle.com; Keller, Jacob E
> <jacob.e.keller@...el.com>; vadfed@...com; johannes@...solutions.net;
> jiri@...nulli.us; dsahern@...nel.org; fw@...len.de; linux-doc@...r.kernel.org
> Subject: Re: [RFC net-next 3/4] ynl: add a sample python library
>
> On Fri, 12 Aug 2022 16:42:53 +0100 Edward Cree wrote:
> > > It would be great if python had standard module for netlink.
> > > Then your code could just (re)use that.
> > > Something like mnl but for python.
> >
> > There's pyroute2, that seemed alright when I used it for something
> > a few years back, and I think it has the pieces you need.
> > https://pyroute2.org/
>
> I saw that and assumed that its true to its name and only supports
> RTNL :( I'll reach out to Peter the maintainer for his thoughts.
>
> This patch was meant as a sample, I kept trying to finish up the C
> codegen for a week and it still didn't feel presentable enough for
> the RFC. In practice I'd rather leave writing the language specific
> libs to the experts.
It has some generic netlink support, but the way it parses messages was a bit confusing to me. It could benefit from the automatic generation of attribute parsing though!
Powered by blists - more mailing lists