| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: re (kib)
|
|
|
|
|
|
|
| |
RAR(0) register does not work on this old adapter,
provide a local routine that does it the older way.
Approved by: re
|
|
|
|
|
|
|
|
| |
result was when the RX index wrapped it was converted into some
sort of gibberish and written into the RDT register, effectively
killing the RX side of the thing :)
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
IF_ADDR_UNLOCK() across network device drivers when accessing the
per-interface multicast address list, if_multiaddrs. This will
allow us to change the locking strategy without affecting our driver
programming interface or binary interface.
For two wireless drivers, remove unnecessary locking, since they
don't actually access the multicast address list.
Approved by: re (kib)
MFC after: 6 weeks
|
|
|
|
|
| |
multiqueue setup which is not the shipping default for
igb (its set to 1).
|
|
|
|
| |
global builds (failing sun4v lint build)
|
| |
|
|
|
|
|
| |
for multiqueue tx, shared code updates, new device
support, and some bug fixes.
|
|
|
|
|
| |
This will bring back improved IPv4 SIOCSIFADDR ioctl handling
not re-initializing the interface if avoidable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CPU for too long period than necessary. Additively, interfaces are kept
polled (in the tick) even if no more packets are available.
In order to avoid such situations a new generic mechanism can be
implemented in proactive way, keeping track of the time spent on any
packet and fragmenting the time for any tick, stopping the processing
as soon as possible.
In order to implement such mechanism, the polling handler needs to
change, returning the number of packets processed.
While the intended logic is not part of this patch, the polling KPI is
broken by this commit, adding an int return value and the new flag
IFCAP_POLLING_NOCOUNT (which will signal that the return value is
meaningless for the installed handler and checking should be skipped).
Bump __FreeBSD_version in order to signal such situation.
Reviewed by: emaste
Sponsored by: Sandvine Incorporated
|
|
|
|
| |
buf_ring on transmit
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
get reset when it should be
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
the watchdog timer was not being rearmed in txeof, and also
a missing case in the new code.
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Pointed out by Nate Whitehorn
|
| |
|
| |
|
|
|
|
|
|
|
| |
few important bug fixes found while they were doing SCTP
development, and that I somehow lost during the scramble.
Thanks guys!!
|
|
|
|
|
|
| |
- make buF_ring usage conditional but enabled by default
Reviewed by: jfv
|
| |
|
|
|
|
|
|
|
| |
adds header split and SCTP support into the igb driver.
Various small improvements and fixes.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
latency tunable.
Reviewed by: jfv
MFC after: 1 day
|
| |
|
|
|
|
|
| |
path for an infinite loop. Problem originally noticed in ixgbe
by Jeff Roberson and fixed there. Thanks to everyone involved.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
will sometimes fail to initialize problem due to a lock
contention with management hardware. However, in order to
deliver that fix it was necessary to take a shared code
update as a whole, and this required scattered changes in
the core code to be compatible.
The em driver now has VLAN HW support added as the igb
driver had previously.
MFC after: ASAP - in time for 7.1 RELEASE
|
|
|
|
| |
MFC after: 2 months
|
|
|
|
| |
MFC after: 2 months
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- changes in support of the VLAN filter fix to 126850
- removal of a bunch of legacy code that was cruft, if not
possibly harmful.
- removal of POLLING from this driver, with multiqueue and
MSIX it just makes no sense here.
- Fix an LRO bug that I've been working on internally, intermittent
panics under stress, the problem was releasing the RX ring lock
before the LRO flushing.
- Following the above fix I now enable LRO by default
- For performance reasons increase the default number of RX queues
to 4.
- Add AIM - "Adaptive Interrupt Moderation", a fancy way of saying
that the EITR value is dynamically changed based on the size of
packets in the last interrupt interval.
- Much goodness to try, enjoy!!
|
| |
|
| |
|
|
proved to be necessary to make the static drivers work
in EITHER/OR or BOTH configurations. Modules will still
build in sys/modules/igb or em as before.
This also updates the igb driver for support for the 82576
adapter, adds shared code fixes, and etc....
MFC after: ASAP
|