From: Patrick McHardy <kaber@trash.net>
To: Bill Nottingham <notting@redhat.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Bridge] [RFC PATCH 0/2] Allow full bridge configuration via sysfs
Date: Mon, 07 Jul 2008 22:50:38 +0200 [thread overview]
Message-ID: <4872819E.3040604@trash.net> (raw)
In-Reply-To: <cover.1215460681.git.notting@redhat.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Bill Nottingham <notting@redhat.com>
Cc: bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] Allow full bridge configuration via sysfs
Date: Mon, 07 Jul 2008 22:50:38 +0200 [thread overview]
Message-ID: <4872819E.3040604@trash.net> (raw)
In-Reply-To: <cover.1215460681.git.notting@redhat.com>
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.
next prev parent reply other threads:[~2008-07-07 20:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 20:05 [Bridge] [RFC PATCH 0/2] Allow full bridge configuration via sysfs Bill Nottingham
2008-07-07 20:05 ` Bill Nottingham
2008-07-07 20:05 ` [Bridge] [PATCH 1/2] Add a 'bridging_masters' file in sysfs under class/net Bill Nottingham
2008-07-07 20:05 ` Bill Nottingham
2008-07-07 20:05 ` [Bridge] [PATCH 2/2] Add a 'interfaces' file to the bridge device configuration in sysfs Bill Nottingham
2008-07-07 20:05 ` Bill Nottingham
2008-07-07 20:50 ` Patrick McHardy [this message]
2008-07-07 20:50 ` [RFC PATCH 0/2] Allow full bridge configuration via sysfs Patrick McHardy
2008-07-07 20:53 ` [Bridge] " Bill Nottingham
2008-07-07 20:53 ` Bill Nottingham
2008-07-07 20:58 ` [Bridge] " Patrick McHardy
2008-07-07 20:58 ` Patrick McHardy
2008-07-07 21:34 ` [Bridge] " Bill Nottingham
2008-07-07 21:34 ` Bill Nottingham
2008-07-07 21:52 ` [Bridge] " David Miller
2008-07-07 21:52 ` David Miller
2008-07-07 22:04 ` [Bridge] " Stephen Hemminger
2008-07-07 22:04 ` Stephen Hemminger
2008-07-10 2:34 ` Bill Nottingham
2008-07-10 2:34 ` Bill Nottingham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4872819E.3040604@trash.net \
--to=kaber@trash.net \
--cc=bridge@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=notting@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.