d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

sfxge(4): comment on when we assume multicast chaining is available

Browse Source 
It's the same on Medford as Huntington.

Multicast chaining is not always on, even with Medford, as it's not
supported by low latency firmware.

Unlike the Linux driver, we don't need to support virtulization with
firmware released before support for multicast chaining was added.

Submitted by:   Mark Spender <mspender at solarflare.com>
Sponsored by:   Solarflare Communications, Inc.
MFC after:      1 week
Differential Revision:  https://reviews.freebsd.org/D6319
This commit is contained in:
Andrew Rybchenko 2016-05-13 06:47:47 +00:00
parent d0a97c000f
commit fe7e969e7a
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
sys/dev/sfxge/common/hunt_filter.c
View File

@ -1191,7 +1191,7 @@ ef10_filter_remove_old(
static __checkReturn efx_rc_t
hunt_filter_get_workarounds(
ef10_filter_get_workarounds(
__in efx_nic_t *enp)
{
efx_nic_cfg_t *encp = &enp->en_nic_cfg;
@ -1319,18 +1319,28 @@ ef10_filter_reconfigure(
* filters, and can only be enabled or disabled when the hardware filter
* table is empty.
*
* Chained multicast filters require support from the datapath firmware,
* and may not be available (e.g. low-latency variants or old Huntington
* firmware).
*
* Firmware will reset (FLR) functions which have inserted filters in
* the hardware filter table when the workaround is enabled/disabled.
* Functions without any hardware filters are not reset.
*
* Re-check if the workaround is enabled after adding unicast hardware
* filters. This ensures that encp->enc_workaround_bug26807 matches the
* filters. This ensures that encp->enc_bug26807_workaround matches the
* firmware state, and that later changes to enable/disable the
* workaround will result in this function seeing a reset (FLR).
*
* FIXME: On Medford multicast chaining should always be on.
* In common-code drivers, we only support multiple PCI function
* scenarios with firmware that supports multicast chaining, so we can
* assume it is enabled for such cases and hence simplify the filter
* insertion logic. Firmware that does not support multicast chaining
* does not support multiple PCI function configurations either, so
* filter insertion is much simpler and the same strategies can still be
* used.
*/
if ((rc = hunt_filter_get_workarounds(enp)) != 0)
if ((rc = ef10_filter_get_workarounds(enp)) != 0)
goto fail2;
if ((table->eft_using_all_mulcst != all_mulcst) &&