will be in the maintainance mode on Wednesday June 29th 01:00 - 10:00 (UTC+1). Repositories is read only during the maintainance.

  1. 12 Jun, 2018 1 commit
    • Jakub Kicinski's avatar
      nfp: remove phys_port_name on flower's vNIC · fe06a64e
      Jakub Kicinski authored
      .ndo_get_phys_port_name was recently extended to support multi-vNIC
      FWs.  These are firmwares which can have more than one vNIC per PF
      without associated port (e.g. Adaptive Buffer Management FW), therefore
      we need a way of distinguishing the vNICs.  Unfortunately, it's too
      late to make flower use the same naming.  Flower users may depend on
      .ndo_get_phys_port_name returning -EOPNOTSUPP, for example the name
      udev gave the PF vNIC was just the bare PCI device-based name before
      the change, and will have 'nn0' appended after.
      To ensure flower's vNIC doesn't have phys_port_name attribute, add
      a flag to vNIC struct and set it in flower code.  New projects will
      not set the flag adhere to the naming scheme from the start.
      Fixes: 51c1df83
       ("nfp: assign vNIC id as phys_port_name of vNICs which are not ports")
      Signed-off-by: default avatarJakub Kicinski <>
      Reviewed-by: default avatarDirk van der Merwe <>
      Reviewed-by: default avatarSimon Horman <>
      Signed-off-by: default avatarDavid S. Miller <>
  2. 23 May, 2018 1 commit
  3. 04 Apr, 2018 1 commit
  4. 06 Feb, 2018 1 commit
  5. 19 Jan, 2018 1 commit
    • Jakub Kicinski's avatar
      nfp: add TLV capabilities to the BAR · 73a0329b
      Jakub Kicinski authored
      NFP is entirely programmable, including the PCI data interface.
      Using a fixed control BAR layout certainly makes implementations
      easier, but require careful considerations when space is allocated.
      Once BAR area is allocated to one feature nothing else can use it.
      Allocating space statically also requires it to be sized upfront,
      which leads to either unnecessary limitation or wastage.
      We currently have a 32bit capability word defined which tells drivers
      which application FW features are supported.   Most of the bits
      are exhausted.  The same bits are also reused for enabling specific
      features.  Bulk of capabilities don't have a need for an enable bit,
      however, leading to confusion and wastage.
      TLVs seems like a better fit for expressing capabilities of applications
      running on programmable hardware.
      This patch leaves the front of the BAR as is, and declares a TLV
      capability start at offset 0x58.  Most of the space up to 0x0d90
      is already allocated, but the used space can be wrapped with RESERVED
      TLVs.  E.g.:
      Address    Type         Length
       0x0058    RESERVED      0xe00  /* Wrap basic structures */
       0x0e5c    FEATURE_A     0x004
       0x0e64    FEATURE_B     0x004
       0x0e6c    RESERVED      0x990  /* Wrap qeueue stats */
       0x1800    FEATURE_C     0x100
      Signed-off-by: default avatarJakub Kicinski <>
      Reviewed-by: default avatarDirk van der Merwe <>
      Signed-off-by: default avatarDavid S. Miller <>
  6. 14 Jan, 2018 1 commit
  7. 05 Jan, 2018 1 commit
  8. 01 Dec, 2017 1 commit
  9. 05 Nov, 2017 1 commit
  10. 02 Nov, 2017 1 commit
  11. 19 Aug, 2017 1 commit
  12. 25 Jun, 2017 1 commit
  13. 23 Jun, 2017 2 commits
  14. 07 Jun, 2017 5 commits
  15. 31 May, 2017 2 commits
  16. 30 May, 2017 1 commit
  17. 22 May, 2017 5 commits
  18. 16 May, 2017 5 commits
  19. 01 May, 2017 3 commits
  20. 24 Apr, 2017 2 commits
  21. 05 Apr, 2017 2 commits
  22. 22 Mar, 2017 1 commit