1. 02 8月, 2017 1 次提交
  2. 05 7月, 2017 1 次提交
    • J
      nfp: default to chained metadata prepend format · 64a919a9
      Jakub Kicinski 提交于
      ABI 4.x introduced the chained metadata format and made it the
      only one possible.  There are cases, however, where the old
      format is preferred - mostly to make interoperation with VFs
      using ABI 3.x easier for the datapath.  In ABI 5.x we allowed
      for more flexibility by selecting the metadata format based
      on capabilities.  The default was left to non-chained.
      
      In case of fallback traffic, there is no capability telling the
      driver there may be chained metadata.  With a very stripped-
      -down FW the default old metadata format would be selected
      making the driver drop all fallback traffic.
      
      This patch changes the default selection in the driver. It
      should not hurt with old firmwares, because if they don't
      advertise RSS they will not produce metadata anyway.  New
      firmwares advertising ABI 5.x, however, can depend on the
      driver defaulting to chained format.
      
      Fixes: f9380629 ("nfp: advertise support for NFD ABI 0.5")
      Suggested-by: NMichael Rapson <michael.rapson@netronome.com>
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      64a919a9
  3. 01 7月, 2017 2 次提交
  4. 25 6月, 2017 1 次提交
  5. 24 6月, 2017 5 次提交
  6. 19 6月, 2017 1 次提交
  7. 16 6月, 2017 1 次提交
  8. 08 6月, 2017 9 次提交
  9. 01 6月, 2017 3 次提交
  10. 30 5月, 2017 3 次提交
  11. 23 5月, 2017 3 次提交
  12. 17 5月, 2017 9 次提交
  13. 03 5月, 2017 1 次提交