[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61eb0c9c-3de7-42da-bd88-f3e63c7d3687@lunn.ch>
Date: Thu, 15 Jun 2023 15:44:30 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Benno Lossin <benno.lossin@...ton.me>
Cc: FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, aliceryhl@...gle.com,
miguel.ojeda.sandonis@...il.com
Subject: Re: [PATCH 2/5] rust: add support for ethernet operations
> > + /// Sets `ethtool_ops` of `net_device`.
> > + pub fn set_ether_operations<U>(&mut self) -> Result
> > + where
> > + U: EtherOperations<D>,
> > + {
> > + if self.is_registered {
> > + return Err(code::EINVAL);
> > + }
> > + EtherOperationsAdapter::<U, D>::new().set_ether_ops(&mut self.dev);
> > + Ok(())
> > + }
>
> Is it really necessary for a device to be able to have multiple different
> `EtherOperations`? Couldnt you also just make `T` implement
> `EtherOperations<D>`?
For 99% of drivers, netdev->ethtool_ops is set once before
register_netdev() is called and never changed.
There is one corner case i know of, and it is a hack:
https://elixir.bootlin.com/linux/v6.4-rc6/source/net/dsa/master.c#L223
Since this is a hack, you can probably skip it in rust.
Andrew
Powered by blists - more mailing lists