On Thu, 16 Mar 2023 23:01:13 +0000 Russell King (Oracle) wrote: > What I would say is be careful with that - make sure "struct bla" is > specific to the interface being called and not generic. > > I had that mistake with struct phylink_state... and there is an > endless stream of people who don't seem to bother reading the > documentation, who blindly access whatever members of that they > damn well please because it suits them, even when either they > shouldn't be writing to them, or when phylink doesn't guarantee > their contents, they read them. Right, gotta take it case by case. I really like structs for const capabilities of the driver / device, which need to be communicated to the core. > As a result, I'm now of the opinion that using a struct to pass > arguments is in principle a bad idea. > > There's other reasons why it's a bad idea. Many ABIs are capable of > passing arguments to functions via processor registers. As soon as > one uses a struct, they typically end up being written to memory. > Not only does that potentially cause cache line churn, it also > means that there could be more slow memory accesses that have to be > made at some point, potentially making other accesses slow. > > So, all in all, I'm really not a fan of the struct approach for > all the reasons above. Also true, one has to be careful on the fast paths. There are cases where similar set of arguments is passed multiple functions down. Making the code hard to follow and extend. But you're right, structs will be slower for the most part. For stmmac I figured it can only help. The driver is touched my very many people, it has layers and confusions...
