Re: [RFC PATCH v0 1/2] net: bridge: propagate FDB table into hardware |
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [RFC PATCH v0 1/2] net: bridge: propagate FDB table into hardware
- From: jamal <hadi@xxxxxxxxxx>
- Date: Thu, 09 Feb 2012 16:11:34 -0500
- Cc: Stephen Hemminger <shemminger@xxxxxxxxxx>, bhutchings@xxxxxxxxxxxxxx, roprabhu@xxxxxxxxx, netdev@xxxxxxxxxxxxxxx, mst@xxxxxxxxxx, chrisw@xxxxxxxxxx, davem@xxxxxxxxxxxxx, gregory.v.rose@xxxxxxxxx, kvm@xxxxxxxxxxxxxxx, sri@xxxxxxxxxx
- In-reply-to: <4F3407F7.9000202@intel.com>
- Reply-to: jhs@xxxxxxxxxxxx
On Thu, 2012-02-09 at 09:52 -0800, John Fastabend wrote:
> >> By netlink_notifier do you mean adding a notifier_block and using atomic_notifier_call_chain()
> >> probably in rtnl_notify()? Then drivers could register with the notifier chain with
> >> atomic_notifier_chain_register() and receive the events correctly. Or did I miss
> >> some notifier chain that already exists?
> >
> > Yes. that is what I mean. The callbacks you need may or may not already be present.
I'll go one step further.
This stuff shouldnt be in the kernel at all.
The disadvantage is you need a user space app to update the hardware.
i.e, the same mechanism should be usable for either a switch embedded
in a NIC or a standalone hardware switch (with/out the s/ware bridge
presence)
cheers,
jamal
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Kernel Discussion]
[Ethernet Bridging]
[Linux Wireless Networking]
[Linux Bluetooth Networking]
[Linux Networking Users]
[VLAN]
[Git]
[IETF Annouce]
[Linux Assembly]
[Security]
[Bugtraq]
[Photo]
[Singles Social Networking]
[Yosemite Information]
[MIPS Linux]
[ARM Linux Kernel]
[ARM Linux]
[Linux Virtualization]
[Linux Security]
[Linux IDE]
[Linux RAID]
[Linux SCSI]
[Free Dating]