src/sys/dev/tsec, branch releng/8.0

Use if_maddr_rlock()/if_maddr_runlock() rather than IF_ADDR_LOCK()/

2009-06-26T11:45:06+00:00

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

Fix Book-E/MPC85XX build. Some prototypes were wrong and got revealed with

2009-06-13T08:57:04+00:00

the recent kobj signature checking.

When user_frac in the polling subsystem is low it is going to busy the

2009-05-30T15:14:44+00:00

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

tsec(4) cosmetics.

2009-02-17T16:02:45+00:00

tsec(4): Always try to resume the receiver.

2009-02-17T15:59:27+00:00

This helps recover from RX stall under heavy loads.

Submitted by:	Piotr Ziecik kosmo ! semihalf dot com

tsec(4): do not clear interrupt events register before use.

2009-02-17T15:47:13+00:00

Prior to this fix, IEVENT register was always cleared before calling
tsec_error_intr_locked(), which prevented error recovery actions from
happening with polling enabled (and could lead to serious problems, including
controller hang).

Submitted by:	Marcin Ligenza marcinl ! pacomp dot com dot pl

Handle mbuf exhaustion scenario in tsec(4).

2009-02-17T15:39:16+00:00

Without this fix the system would hang under heavy networking load.

Submitted by:	Leon Theunissen leon ! parsec dot co dot za

tsec(4) style improvements and clean-up.

2009-02-17T14:59:47+00:00

Additional features for the tsec(4) Ethernet driver.

2009-02-17T14:57:05+00:00

  - interrupt coalescing
  - polling
  - jumbo frames
  - multicast
  - VLAN tagging

The enhanced version of the chip (eTSEC) can also take advantage of:

  - TCP/IP checksum calculation h/w offloading

Obtained from:	Freescale, Semihalf

tsec: Refactor driver's structure.

2008-08-26T10:41:49+00:00

Split the driver into the core functionality part (sys/dev/tsec/if_tsec.c) and
the bus attachment (sys/dev/tsec/if_tsec_ocp.c).

This lets better integrate and maintain the driver in other environments with
different attachment abstractions (there is at least one other FreeBSD port --
MPC83xx -- which uses this TSEC driver, but with different local bus model
i.e. some OF derivative). While there, clean up and fix minor cosmetics.

Obtained from:	Semihalf