| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
interface. The check itself seems to be coming from OpenBSD but does not
seem to be useful for our code.
Discussed with: thomasa
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
do initialization of hw related features.
PR: kern/141646
Reviewed by: thompsa
Approved by: thompsa(co-mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
address on an interface has changed. This lets stacked interfaces such as
vlan(4) detect that their lower interface has changed and adjust things in
order to keep working. Previously this situation broke at least vlan(4) and
lagg(4) configurations.
The EVENTHANDLER_INVOKE call was not placed within if_setlladdr() due to the
risk of a loop.
PR: kern/142927
Submitted by: Nikolay Denev
|
| |
|
| |
|
|
|
|
|
|
| |
to allow passing a cached struct llentry * down to L2
Reviewed by: rwatson
|
|
|
|
| |
- Initialise speed where its used
|
|
|
|
| |
different aggregation protocols.
|
|
|
|
| |
Submitted by: Tom Hicks (thicks_averesys.com)
|
| |
|
|
|
|
|
|
|
|
| |
belongs solely to the driver.
We don't lose any statistics with this change, because in a error
case the drop counter on the interface output queue is always incremented.
Reviewed by: thompsa
|
|
|
|
| |
can not change while we have the lock so no point retesting.
|
|
|
|
|
|
|
| |
tx port.
PR: kern/122794
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
this means that it no longer grabs the lagg rwlock. Use two port table arrays
which list the active ports for Tx and switch between them with an atomic op.
Now the lagg rwlock is only exclusively locked for management (ioctls) and
queuing of lacp control frames isnt needed.
|
|
|
|
| |
there are more subtypes than just LACP.
|
|
|
|
|
|
|
|
|
| |
administratively down (!IFF_UP)
- Use the same parameters to lagg_link_active() to get the backup port as in
the output path, this didnt actually matter in practice as sc_primary is
always the first on the port list.
MFC after: 3 days
|
| |
|
|
|
|
| |
processing.
|
|
|
|
|
|
|
|
| |
as up if at least one of its ports also has a link up. This fixes using
carp+lagg together and any other system that relies on linkstate events.
PR: kern/113956
MFC after: 3 days
|
|
|
|
|
|
| |
under a vlan.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. The locking was changed to shared but roundrobin mode still updated a
pointer in the softc with the next tx interface to use. This will panic
under high load. Change this to an atomically incremented sequence number in
order to choose the tx port in round robin.
2. IFQ_HANDOFF will free the mbuf if the queue is full, this will then be freed
again by lagg_start() and panic. Reorganised the error handling and freeing
to fix this.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
active in failover mode rather than all interfaces with a link. This makes it
clear if the master interface is in use or one of the backup links.
Found by: Writing the Handbook section
Approved by: re (kensmith)
|
|
|
|
|
|
|
|
|
|
|
| |
ports to the lagg interface.
- Use the MTU from the first interface as the lagg MTU, all extra interfaces
must be the same.
This fixes using a lagg interface for a vlan or enabling jumbo frames, etc.
Approved by: re (kensmith)
MFC After: 3 days
|
|
|
|
|
| |
Reported by: dfr
Approved by: re (rwatson)
|
|
|
|
|
|
|
| |
actor and partner peer info. Print out the active aggregator and per port data
in verbose mode from ifconfig.
Approved by: re (mux)
|
|
|
|
|
|
|
| |
- remove dead code
- use consistent variable names
- gc unused defines
- whitespace cleanup
|
|
|
|
| |
- Use IFQ_HANDOFF instead of rolling our own
|
| |
|
| |
|
|
|
|
| |
Reported by: Artem Naluzhny, Frank Terhaar-Yonkers
|
|
|
|
| |
Obtained from: NetBSD
|
|
|
|
|
| |
selected simultaneously by multiple senders and transmit/receive is not
serialised between aggregated interfaces.
|
|
|
|
|
| |
- Remove lagg_ether_purgemulti as its no longer needed
- Mark the interface as up if any ports are active rather than just the primary
|
|
|
|
| |
detached.
|
|
|
|
|
| |
is not held. The short delay between aggregating the port and setting the MAC
address is fine.
|
| |
|
|
|
|
|
|
| |
and is safe to use if the ifp has disappeared.
Suggested by: bms
|
|
|
|
| |
- Refine check for lacp links, set to disabled if not suitable
|
| |
|
|
The name trunk is misused as the networking term trunk means carrying multiple
VLANs over a single connection. The IEEE standard for link aggregation (802.3
section 3) does not talk about 'trunk' at all while it is used throughout IEEE
802.1Q in describing vlans.
The lagg(4) driver provides link aggregation, failover and fault tolerance.
Discussed on: current@
|