[RFC v3 4/6] bridge: enable root block during device registration

2014-03-03 Thread Luis R. Rodriguez
From: Luis R. Rodriguez mcg...@suse.com root block support was added via 1007dd1a on v3.8 but toggling this flag is only allowed after a device has been registered and added to a bridge as its a bridge *port* primitive, not a *net_device* feature. There are work arounds possible to account for

Re: [RFC v3 4/6] bridge: enable root block during device registration

2014-03-03 Thread Stephen Hemminger
On Mon, 3 Mar 2014 14:47:03 -0800 Luis R. Rodriguez mcg...@do-not-panic.com wrote: From: Luis R. Rodriguez mcg...@suse.com root block support was added via 1007dd1a on v3.8 but toggling this flag is only allowed after a device has been registered and added to a bridge as its a bridge

Re: [RFC v3 4/6] bridge: enable root block during device registration

2014-03-03 Thread Luis R. Rodriguez
On Mon, Mar 3, 2014 at 3:43 PM, Stephen Hemminger step...@networkplumber.org wrote: Doing this in priv flags bloats what is a limited resource (# of bits). Agreed. I tried to avoid it but saw no other option for addressing this during initialization properly without requirng a userspace upgrade.

Re: [RFC v3 4/6] bridge: enable root block during device registration

2014-03-03 Thread Stephen Hemminger
On Mon, 3 Mar 2014 15:58:50 -0800 Luis R. Rodriguez mcg...@do-not-panic.com wrote: On Mon, Mar 3, 2014 at 3:43 PM, Stephen Hemminger step...@networkplumber.org wrote: Doing this in priv flags bloats what is a limited resource (# of bits). Agreed. I tried to avoid it but saw no other

Re: [RFC v3 4/6] bridge: enable root block during device registration

2014-03-03 Thread Luis R. Rodriguez
On Mon, Mar 3, 2014 at 4:31 PM, Stephen Hemminger step...@networkplumber.org wrote: On Mon, 3 Mar 2014 15:58:50 -0800 Luis R. Rodriguez mcg...@do-not-panic.com wrote: On Mon, Mar 3, 2014 at 3:43 PM, Stephen Hemminger step...@networkplumber.org wrote: Doing this in priv flags bloats what is