1. 10 6月, 2017 1 次提交
  2. 22 5月, 2017 1 次提交
  3. 09 5月, 2017 1 次提交
  4. 21 4月, 2017 1 次提交
  5. 03 2月, 2017 1 次提交
  6. 08 10月, 2016 2 次提交
    • S
      iw_cxgb4: add fast-path for small REG_MR operations · 49b53a93
      Steve Wise 提交于
      When processing a REG_MR work request, if fw supports the
      FW_RI_NSMR_TPTE_WR work request, and if the page list for this
      registration is <= 2 pages, and the current state of the mr is INVALID,
      then use FW_RI_NSMR_TPTE_WR to pass down a fully populated TPTE for FW
      to write.  This avoids FW having to do an async read of the TPTE blocking
      the SQ until the read completes.
      
      To know if the current MR state is INVALID or not, iw_cxgb4 must track the
      state of each fastreg MR.  The c4iw_mr struct state is updated as REG_MR
      and LOCAL_INV WRs are posted and completed, when a reg_mr is destroyed,
      and when RECV completions are processed that include a local invalidation.
      
      This optimization increases small IO IOPS for both iSER and NVMF.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      49b53a93
    • S
      cxgb4: advertise support for FR_NSMR_TPTE_WR · 086de575
      Steve Wise 提交于
      Query firmware for the FW_PARAMS_PARAM_DEV_RI_FR_NSMR_TPTE_WR parameter.
      If it exists and is 1, then advertise support for FR_NSMR_TPTE_WR to
      the ULDs.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      086de575
  7. 21 9月, 2016 1 次提交
  8. 23 8月, 2016 1 次提交
  9. 19 8月, 2016 2 次提交
  10. 26 7月, 2016 1 次提交
  11. 27 4月, 2016 1 次提交
  12. 22 3月, 2016 1 次提交
  13. 01 3月, 2016 1 次提交
    • H
      cxgb4/iw_cxgb4: TOS support · ac8e4c69
      Hariprasad S 提交于
      This series provides support for iWARP applications to specify a TOS
      value and have that map to a VLAN Priority for iw_cxgb4 iWARP connections.
      
      In iw_cxgb4, when allocating an L2T entry, pass the skb_priority based
      on the tos value in the cm_id. Also pass the correct tos value during
      connection setup so the passive side gets the client's desired tos.
      When sending the FLOWC work request to FW, if the egress device is
      in a vlan, then use the vlan priority bits as the scheduling class.
      This allows associating RDMA connections with scheduling classes to
      provide traffic shaping per flow.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NHariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      ac8e4c69
  14. 11 2月, 2016 1 次提交
    • H
      cxgb4/iw_cxgb4: TOS support · ba9cee6a
      Hariprasad Shenai 提交于
      This series provides support for iWARP applications to specify a TOS
      value and have that map to a VLAN Priority for iw_cxgb4 iWARP connections.
      
      In iw_cxgb4, when allocating an L2T entry, pass the skb_priority based
      on the tos value in the cm_id. Also pass the correct tos value during
      connection setup so the passive side gets the client's desired tos.
      When sending the FLOWC work request to FW, if the egress device is
      in a vlan, then use the vlan priority bits as the scheduling class.
      This allows associating RDMA connections with scheduling classes to
      provide traffic shaping per flow.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NHariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ba9cee6a
  15. 10 9月, 2015 1 次提交
  16. 06 6月, 2015 1 次提交
  17. 02 6月, 2015 1 次提交
  18. 25 5月, 2015 1 次提交
  19. 13 5月, 2015 1 次提交
  20. 06 5月, 2015 2 次提交
  21. 02 4月, 2015 1 次提交
  22. 09 3月, 2015 1 次提交
  23. 10 2月, 2015 1 次提交
  24. 08 2月, 2015 1 次提交
  25. 25 1月, 2015 1 次提交
  26. 09 1月, 2015 1 次提交
  27. 19 12月, 2014 1 次提交
  28. 13 12月, 2014 2 次提交
  29. 23 11月, 2014 5 次提交
  30. 14 11月, 2014 1 次提交
  31. 11 11月, 2014 1 次提交
  32. 02 9月, 2014 1 次提交