public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: bridge@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] Allow full bridge configuration via sysfs
Date: Mon,  7 Jul 2008 16:05:02 -0400	[thread overview]
Message-ID: <cover.1215460681.git.notting@redhat.com> (raw)

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.)

Patchset is against net-next-2.6, but should apply to anything reasonably
recent with minimal fuzz.

Bill Nottingham (2):
  Add a 'bridging_masters' file in sysfs under class/net
  Add a 'interfaces' file to the bridge device configuration in sysfs

 net/bridge/br.c          |    2 +
 net/bridge/br_private.h  |    4 ++
 net/bridge/br_sysfs_br.c |  136 ++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 142 insertions(+), 0 deletions(-)


             reply	other threads:[~2008-07-07 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 20:05 Bill Nottingham [this message]
2008-07-07 20:05 ` [PATCH 1/2] Add a 'bridging_masters' file in sysfs under class/net Bill Nottingham
2008-07-07 20:05 ` [PATCH 2/2] Add a 'interfaces' file to the bridge device configuration in sysfs Bill Nottingham
2008-07-07 20:50 ` [RFC PATCH 0/2] Allow full bridge configuration via sysfs Patrick McHardy
2008-07-07 20:53   ` Bill Nottingham
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=cover.1215460681.git.notting@redhat.com \
    --to=notting@redhat.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=linux-kernel@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