1. 21 3月, 2022 5 次提交
  2. 12 3月, 2022 5 次提交
  3. 04 3月, 2022 3 次提交
  4. 22 11月, 2021 1 次提交
  5. 26 7月, 2021 1 次提交
  6. 15 7月, 2020 1 次提交
  7. 20 12月, 2019 1 次提交
    • J
      nfp: tls: implement the stream sync RX resync · 6a35ddc5
      Jakub Kicinski 提交于
      The simple RX resync strategy controlled by the kernel does not
      guarantee as good results as if the device helps by detecting
      the potential record boundaries and keeping track of them.
      
      We've called this strategy stream scan in the tls-offload doc.
      
      Implement this strategy for the NFP. The device sends a request
      for record boundary confirmation, which is then recorded in
      per-TLS socket state and responded to once record is reached.
      Because the device keeps track of records passing after the
      request was sent the response is not as latency sensitive as
      when kernel just tries to tell the device the information
      about the next record.
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6a35ddc5
  8. 31 8月, 2019 1 次提交
  9. 09 7月, 2019 1 次提交
  10. 06 7月, 2019 1 次提交
  11. 12 6月, 2019 3 次提交
  12. 07 6月, 2019 6 次提交
  13. 13 4月, 2019 1 次提交
  14. 01 12月, 2018 2 次提交
  15. 20 11月, 2018 1 次提交
  16. 09 11月, 2018 1 次提交
  17. 12 10月, 2018 1 次提交
  18. 26 7月, 2018 2 次提交
  19. 14 7月, 2018 2 次提交
  20. 13 6月, 2018 1 次提交