1. 24 7月, 2020 1 次提交
    • J
      sfc: convert to new udp_tunnel infrastructure · 205a55f4
      Jakub Kicinski 提交于
      Check MC_CMD_DRV_ATTACH_EXT_OUT_FLAG_TRUSTED, before setting
      the info, which will hopefully protect us from -EPERM errors
      the previous code was gracefully ignoring. Ed reports this
      is not the 100% correct bit, but it's the best approximation
      we have. Shared code reports the port information back to user
      space, so we really want to know what was added and what failed.
      Ignoring -EPERM is not an option.
      
      The driver does not call udp_tunnel_get_rx_info(), so its own
      management of table state is not really all that problematic,
      we can leave it be. This allows the driver to continue with its
      copious table syncing, and matching the ports to TX frames,
      which it will reportedly do one day.
      
      Leave the feature checking in the callbacks, as the device may
      remove the capabilities on reset.
      
      Inline the loop from __efx_ef10_udp_tnl_lookup_port() into
      efx_ef10_udp_tnl_has_port(), since it's the only caller now.
      
      With new infra this driver gains port replace - when space frees
      up in a full table a new port will be selected for offload.
      Plus efx will no longer sleep in an atomic context.
      
      v2:
       - amend the commit message about TRUSTED not being 100%
       - add TUNNEL_ENCAP_UDP_PORT_ENTRY_INVALID to mark unsed
         entries
      Signed-off-by: NJakub Kicinski <kuba@kernel.org>
      Acked-By: NEdward Cree <ecree@solarflare.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      205a55f4
  2. 03 7月, 2020 6 次提交
  3. 01 7月, 2020 2 次提交
  4. 30 6月, 2020 4 次提交
  5. 02 6月, 2020 1 次提交
  6. 29 5月, 2020 1 次提交
  7. 12 5月, 2020 6 次提交
  8. 06 3月, 2020 1 次提交
    • T
      sfc: complete the next packet when we receive a timestamp · 3b4f06c7
      Tom Zhao 提交于
      We now ignore the "completion" event when using tx queue timestamping,
      and only pay attention to the two (high and low) timestamp events. The
      NIC will send a pair of timestamp events for every packet transmitted.
      The current firmware may merge the completion events, and it is possible
      that future versions may reorder the completion and timestamp events.
      As such the completion event is not useful.
      
      Without this patch in place a merged completion event on a queue with
      timestamping will cause a "spurious TX completion" error. This affects
      SFN8000-series adapters.
      Signed-off-by: NTom Zhao <tzhao@solarflare.com>
      Acked-by: NMartin Habets <mhabets@solarflare.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3b4f06c7
  9. 27 1月, 2020 3 次提交
  10. 11 1月, 2020 4 次提交
  11. 10 1月, 2020 4 次提交
  12. 09 1月, 2020 2 次提交
  13. 06 1月, 2020 1 次提交
  14. 23 11月, 2019 1 次提交
    • E
      sfc: suppress MCDI errors from ARFS · 0aa6608d
      Edward Cree 提交于
      In high connection count usage, the NIC's filter table may be filled with
       sufficiently many ARFS filters that further insertions fail.  As this
       does not represent a correctness issue, do not log the resulting MCDI
       errors.  Add a debug-level message under the (by default disabled)
       rx_status category instead; and take the opportunity to do a little extra
       expiry work.
      
      Since there are now multiple workitems able to call __efx_filter_rfs_expire
       on a given channel, it is possible for them to race and thus pass quotas
       which, combined, exceed rfs_filter_count.  Thus, don't WARN_ON if we loop
       all the way around the table with quota left over.
      Signed-off-by: NEdward Cree <ecree@solarflare.com>
      Tested-by: NDavid Ahern <dahern@digitalocean.com>
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      0aa6608d
  15. 01 11月, 2019 1 次提交
  16. 25 7月, 2019 1 次提交
  17. 19 6月, 2019 1 次提交