7 Nov
2024
7 Nov
'24
3:59 p.m.
On Thu, 7 Nov 2024 22:11:24 +0800 Xiao Liang wrote:
Instead, add new rtnetlink attributes ?
It is to control driver behavior at rtnl_ops registration time. I think rtnetlink attributes are too late for that, maybe? Can't think of a way other than module parameters or register separate ops. Any suggestions?
Step back from the implementation you have a little, forget that there is a boolean in rtnl_link_ops. User makes a request to spawn an interface, surely a flag inside that request can dictate how the netns attrs are interpreted.