Re: [RFC PATCH v4 2/4] dpll: Add DPLL framework base functions

Sat, Dec 03, 2022 at 06:22:06AM CET, kuba@kernel.org wrote:

On Fri, 2 Dec 2022 17:15:23 +0100 Jiri Pirko wrote:

quoted

quoted

OK, I now see your point what is the confusion.
Thanks for explanation.
But I am still not sure how to make it this way in Linux, if interface added to
netns uses original netdev ifindex, and driver after reload receives new
(previously unused ifindex) what would be the steps/commands to make it as you
described?

As I said, I don't see a way to have the ifindex exposed throught dpll
at all.

We can quite easily only report ifindexes in the same namespace
as the socket, right?

Sure, hmm, thinkign about it more, this would be probably a good start.

quoted

I believe we should do it only the other way around. Assign
dpll_pin pointer to struct net_device and expose this over new attr
IFLA_DPLL_PIN over RT netlink.

The ID table is global, what's the relationship between DPLLs
and net namespaces? We tie DPLLs to a devlink instance which
has a namespace? We pretend namespaces don't exist? :S

Well, if would be odd to put dpll itself into a namespace. It might not
have anything to do with networking, for example in case of ptp_ocp.
What would mean for a dpll to be in a net namespace?