From: Bill Nottingham <notting@redhat.com>
To: Patrick McHardy <kaber@trash.net>
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, 7 Jul 2008 16:53:42 -0400 [thread overview]
Message-ID: <20080707205342.GA19710@nostromo.devel.redhat.com> (raw)
In-Reply-To: <4872819E.3040604@trash.net>
Patrick McHardy (kaber@trash.net) said:
> 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.
How does that improve the situation for bridge devices? Are all
bridging parameters (forward_delay, stp, etc.) going to be configurable
via netlink, or would we still then have multiple tools/interfaces
to configuration? Also, moving bonding configuration to netlink seems
like a step backwards.
Bill
next prev parent reply other threads:[~2008-07-07 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1215460681.git.notting@redhat.com>
2008-07-07 20:50 ` [RFC PATCH 0/2] Allow full bridge configuration via sysfs Patrick McHardy
2008-07-07 20:53 ` Bill Nottingham [this message]
2008-07-07 20:58 ` Patrick McHardy
2008-07-07 21:34 ` Bill Nottingham
2008-07-07 21:52 ` David Miller
2008-07-07 22:04 ` [Bridge] " Stephen Hemminger
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=20080707205342.GA19710@nostromo.devel.redhat.com \
--to=notting@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).