> > The idea of having the PHY/network device as a cooling agent is > something valuable, but as Andrew pointed out, you need to expose this > as a standard HWMON device, and you need to let user-space implement the > appropriate thermal policy, not do that in the network driver underneath > the user's feet with no feedback other than link dropped, got > re-negotiated at a different speed. How would one be able to > differentiate those events from a faulty link partner for instance?
> > None of what you are doing here is specific to your device driver and > the policy of downgrading the link speed to lower the thermal budget is > something that is nearly universally applicable to all network > equipments because higher speeds just require higher power. > Hi Florian, Partially agreed with you, but as far as I know there is no much of ready to use infrastructure for this to use right now? IMHO that could be a both-way solution, where short term driver patch will secure against hardware burn out right now, and long term hwmon based infrastructure could handle that on userspace level. A whole separate concern is how much userspace should be involved here. It could be a very device specific (and therefore driver specific) logic on how to do device's thermal control. Regards, Igor
