> -----Original Message----- > From: [email protected] [mailto:netdev- > [email protected]] On Behalf Of Casey Leedom > Sent: Thursday, July 06, 2017 2:54 PM > To: Jakub Kicinski <[email protected]> > Cc: Dustin Byford <[email protected]>; Andrew Lunn > <[email protected]>; Roopa Prabhu <[email protected]>; > [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; Manoj Malviya > <[email protected]>; Santosh Rastapur <[email protected]>; > [email protected]; [email protected]; [email protected]; > [email protected]; Kirsher, Jeffrey T <[email protected]> > Subject: Re: [PATCH net-next 1/3] net: ethtool: add support for forward error > correction modes > > | From: Jakub Kicinski <[email protected]> > | Sent: Thursday, July 6, 2017 12:02 PM > | > | IMHO if something gets replugged all the settings should be reset. > | I feel that it's not entirely unlike replugging a USB adapter. Perhaps > | we should introduce some (devlink) notifications for SFP module events > | so userspace can apply whatever static user config it has? > > Absolutely a valid approach. As are all of the ones I outlined. > [..] > As I noted in my previous letter: this is something new that we've never > faced before with any prior networking technology. All previous networking > technologies had a static set of Physical Port Capabilities fixed from the > moment a Host Diver/Firmware first see a Port. We're now facing a situation > where these can change dynamically from moment to moment based on what > Transceiver Module is inserted.
Agree with your points generally, but other networking hw vendors have dealt with this since SFP variant and other modules arrived on the scene.
