On Thu, Sep 24, 2015 at 6:23 PM, Florian Fainelli <f.faine...@gmail.com> wrote: > On 24/09/15 13:59, sfel...@gmail.com wrote: >> From: Scott Feldman <sfel...@gmail.com> >> >> Push bridge-level attributes down to switchdev drivers. This patchset >> adds the infrastructure and then pushes, as an example, ageing_time attribute >> down from bridge to switchdev (rocker) driver. Add some range-checking >> for ageing_time. >> >> # ip link set dev br0 type bridge ageing_time 1000 >> >> # ip link set dev br0 type bridge ageing_time 999 >> RTNETLINK answers: Numerical result out of range >> >> Up until now, switchdev attrs where port-level attrs, so the netdev used in >> switchdev_attr_set() would be a switch port or bond of switch ports. With >> bridge-level attrs, the netdev passed to switchdev_attr_set() is the bridge >> netdev. The same recusive algo is used to visit the leaves of the stacked >> drivers to set the attr, it's just in this case we start one layer higher in >> the stack. One note is not all ports in the bridge may support setting a >> bridge-level attribute, so rather than failing the entire set, we'll skip >> over >> those ports returning -EOPNOTSUPP. > > So, without a better device to hold that kind of information (in the > future it could be a global, switch-specific device holding that > information), I agree with your decision to take the bridge device to > hold that attribute, it still feels a bit uncomfortable to have > switchdev_attr_port() take a bridge device parameter, but whatever, here > is a scenario I am wondering how we would want to proceed with: > > - suppose we have a switch which is only able to control ageing > globally, not per port or any other kind of logical domain > > - we have enabled two software bridges on the same physical switch, with > different ageing timeouts > > It does not seem to me like it hurts ageing the other bridge faster than > expected (even though that could be expensive for MDIO devices), but we > would need to have consistent reporting here for the other bridge.
It could hurt a little bit by ageing out entries prematurely, forcing relearning. ;) I think if the switch can't support multiple ageing timeouts (which is probably typical), then the switch driver should not implement this switchdev attr at the port level (this patchset). So how does ageing timeout get set for a switch with a global timer? I believe we need the switch-specific device to handle those switch-global attr sets. I'll send out a refresh of my RFC patches for switch device class, and add this ageing_time attr. -- 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
