Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757562AbYGGUuw (ORCPT ); Mon, 7 Jul 2008 16:50:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756034AbYGGUum (ORCPT ); Mon, 7 Jul 2008 16:50:42 -0400 Received: from stinky.trash.net ([213.144.137.162]:38142 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755827AbYGGUul (ORCPT ); Mon, 7 Jul 2008 16:50:41 -0400 Message-ID: <4872819E.3040604@trash.net> Date: Mon, 07 Jul 2008 22:50:38 +0200 From: Patrick McHardy User-Agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080405) MIME-Version: 1.0 To: Bill Nottingham CC: bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Linux Netdev List Subject: Re: [RFC PATCH 0/2] Allow full bridge configuration via sysfs References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 920 Lines: 20 Bill Nottingham wrote: > Right now, you can configure most bridge device parameters via sysfs. > However, you cannot either: > - add or remove bridge interfaces > - add or remove physical interfaces from a bridge > > The attached patch set rectifies this. With this patch set, brctl > (theoretically) becomes completely optional, much like ifenslave is > now for bonding. (In fact, the idea for this patch, and the syntax > used herein, is inspired by the sysfs bonding configuration.) Both should use netlink instead of extending their sysfs interfaces. For bridging I have a patch for the bridge device itself, the API is so far missing support for adding ports though. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/