From: Casey Leedom <lee...@chelsio.com> Date: Thu, 21 May 2015 16:36:00 +0000
> I definitely understand the issue of wanting to avoid randomly > different module parameters in various drivers which do similar > things. What we're looking for is a list of the acceptable ways for > doing things ― especially when they don't fit current > ethtool/ioctl() mechanisms. The prevailing assumption is that it's OK to have configuration settings that can't be undone. And that's bogus from the beginning. Drivers that have such situations are extremely painful for large scale organizations, and I think you probably have no idea how much of a huge hassle is created by features that can't be undone or disabled at run time. It is not feasible to reboot every machine in one's datacenter to turn off a feature that's causing problems. Yet that's what some large scale organizations end up having to do, and it's COMPLETELY NOT ACCEPTABLT that they have to do this. So instead of trying to figure out ways to use things other than ethtool, work instead to eliminate all situations where a feature cannot be disabled/undone after probe time. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
