From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 3 Mar 2014 16:31:59 -0800 From: Stephen Hemminger Message-ID: <20140303163159.365d763b@nehalam.linuxnetplumber.net> In-Reply-To: References: <1393886825-24323-1-git-send-email-mcgrof@do-not-panic.com> <1393886825-24323-5-git-send-email-mcgrof@do-not-panic.com> <20140303154330.238a20bc@nehalam.linuxnetplumber.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [RFC v3 4/6] bridge: enable root block during device registration List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Luis R. Rodriguez" Cc: "netdev@vger.kernel.org" , bridge@lists.linux-foundation.org, "linux-kernel@vger.kernel.org" , kvm@vger.kernel.org, xen-devel@lists.xenproject.org On Mon, 3 Mar 2014 15:58:50 -0800 "Luis R. Rodriguez" wrote: > On Mon, Mar 3, 2014 at 3:43 PM, Stephen Hemminger > 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. Replacing one Xen hack for another doesn't seem like great progress. I would rather see an API change as needed because there are other things like setting STP parameters which might also want to be part of initial device add.