1. 13 3月, 2017 9 次提交
  2. 10 3月, 2017 4 次提交
  3. 21 2月, 2017 2 次提交
  4. 11 2月, 2017 4 次提交
  5. 05 11月, 2016 5 次提交
  6. 01 11月, 2016 6 次提交
  7. 22 9月, 2016 3 次提交
  8. 30 6月, 2016 1 次提交
  9. 17 4月, 2016 1 次提交
    • J
      nfp: add async reconfiguration mechanism · 3d780b92
      Jakub Kicinski 提交于
      Some callers of nfp_net_reconfig() are in atomic context so
      we used to busy wait for commands to complete.  In worst case
      scenario that means locking up a core for up to 5 seconds
      when a command times out.  Lets add a timer-based mechanism
      of asynchronously checking whether reconfiguration completed
      successfully for atomic callers to use.  Non-atomic callers
      can now just sleep.
      
      The approach taken is quite simple because (1) synchronous
      reconfigurations always happen under RTNL (or before device
      is registered); (2) we can coalesce pending reconfigs.
      There is no need for request queues, timer which eventually
      takes a look at reconfiguration result to report errors is
      good enough.
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3d780b92
  10. 09 4月, 2016 3 次提交
  11. 02 3月, 2016 1 次提交
  12. 04 12月, 2015 1 次提交