1. 08 11月, 2018 5 次提交
  2. 01 11月, 2018 2 次提交
  3. 23 10月, 2018 1 次提交
  4. 11 10月, 2018 2 次提交
  5. 06 10月, 2018 1 次提交
  6. 29 9月, 2018 1 次提交
  7. 22 9月, 2018 5 次提交
  8. 20 9月, 2018 4 次提交
  9. 04 8月, 2018 1 次提交
  10. 07 7月, 2018 1 次提交
  11. 02 7月, 2018 2 次提交
  12. 29 6月, 2018 3 次提交
  13. 07 6月, 2018 1 次提交
  14. 06 6月, 2018 1 次提交
  15. 02 6月, 2018 3 次提交
  16. 29 5月, 2018 1 次提交
  17. 21 5月, 2018 1 次提交
  18. 16 5月, 2018 2 次提交
  19. 11 5月, 2018 1 次提交
  20. 23 3月, 2018 2 次提交
    • S
      net: hns3: Changes to support ARQ(Asynchronous Receive Queue) · 07a0556a
      Salil Mehta 提交于
      Current mailbox CRQ could consists of both synchronous and async
      responses from the PF. Synchronous responses are time critical
      and should be handed over to the waiting tasks/context as quickly
      as possible otherwise timeout occurs.
      
      Above problem gets accentuated if CRQ consists of even single
      async message. Hence, it is important to have quick handling of
      synchronous messages and maybe deferred handling of async messages
      This patch introduces separate ARQ(async receive queues) for the
      async messages. These messages are processed later with repsect
      to mailbox task while synchronous messages still gets processed
      in context to mailbox interrupt.
      
      ARQ is important as VF reset introduces some new async messages
      like MBX_ASSERTING_RESET which adds up to the presssure on the
      responses for synchronousmessages and they timeout even more
      quickly.
      Signed-off-by: NSalil Mehta <salil.mehta@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      07a0556a
    • S
      net: hns3: Add support to re-initialize the hclge device · 7a01c897
      Salil Mehta 提交于
      After the hardware reset we should re-fetch the configuration from
      PF like queue info and tc info. This might have impact on allocations
      made like that of TQPs. Hence, we should release all such allocations
      and re-allocate fresh according to new fetched configuration after
      reset.
      Signed-off-by: NSalil Mehta <salil.mehta@huawei.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7a01c897