RFC Allow full bridge configuration via sysfs
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Add a 'bridging_masters' file in sysfs under class/netnet/ net/ net/ | +77 | 0 replies | |
| 2/2 | Add a 'interfaces' file to the bridge device configuration in sysfsnet/ | +65 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] Allow full bridge configuration via sysfs
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(-)