[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150924140525.514eac85@urahara>
Date: Thu, 24 Sep 2015 14:05:25 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: sfeldma@...il.com
Cc: netdev@...r.kernel.org, jiri@...nulli.us,
siva.mannem.lnx@...il.com, pjonnala@...adcom.com,
roopa@...ulusnetworks.com, andrew@...n.ch, f.fainelli@...il.com,
vivien.didelot@...oirfairelinux.com
Subject: Re: [PATCH net-next 0/4] switchdev: push bridge attributes down
On Thu, 24 Sep 2015 13:59:26 -0700
sfeldma@...il.com wrote:
> From: Scott Feldman <sfeldma@...il.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.
Rather than having more in bridge, shouldn't this just be a netlink event?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists