1. 02 9月, 2015 1 次提交
  2. 10 6月, 2015 1 次提交
  3. 11 4月, 2015 3 次提交
  4. 10 4月, 2015 1 次提交
  5. 14 3月, 2015 1 次提交
  6. 06 2月, 2015 2 次提交
  7. 31 12月, 2014 1 次提交
  8. 06 12月, 2014 3 次提交
  9. 02 10月, 2014 1 次提交
  10. 18 9月, 2014 2 次提交
  11. 12 9月, 2014 1 次提交
    • A
      ixgbe: Refactor busy poll socket code to address multiple issues · adc81090
      Alexander Duyck 提交于
      This change addresses several issues in the current ixgbe implementation of
      busy poll sockets.
      
      First was the fact that it was possible for frames to be delivered out of
      order if they were held in GRO.  This is addressed by flushing the GRO buffers
      before releasing the q_vector back to the idle state.
      
      The other issue was the fact that we were having to take a spinlock on
      changing the state to and from idle.  To resolve this I have replaced the
      state value with an atomic and use atomic_cmpxchg to change the value from
      idle, and a simple atomic set to restore it back to idle after we have
      acquired it.  This allows us to only use a locked operation on acquiring the
      vector without a need for a locked operation to release it.
      Signed-off-by: NAlexander Duyck <alexander.h.duyck@intel.com>
      Tested-by: NPhil Schmitt <phillip.j.schmitt@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      adc81090
  12. 27 5月, 2014 1 次提交
  13. 23 5月, 2014 1 次提交
  14. 23 4月, 2014 1 次提交
  15. 19 4月, 2014 1 次提交
  16. 11 4月, 2014 1 次提交
  17. 01 4月, 2014 2 次提交
  18. 13 3月, 2014 1 次提交
  19. 03 3月, 2014 1 次提交
  20. 01 3月, 2014 1 次提交
  21. 18 1月, 2014 1 次提交
  22. 15 1月, 2014 3 次提交
  23. 18 12月, 2013 1 次提交
  24. 08 11月, 2013 1 次提交
  25. 01 11月, 2013 1 次提交
  26. 29 10月, 2013 1 次提交
    • J
      ixgbe: fix qv_lock_napi call in ixgbe_napi_disable_all · 27d9ce4f
      Jacob Keller 提交于
      ixgbe_napi_disable_all calls napi_disable on each queue, however the busy
      polling code introduced a local_bh_disable()d context around the napi_disable.
      The original author did not realize that napi_disable might sleep, which would
      cause a sleep while atomic BUG. In addition, on a single processor system, the
      ixgbe_qv_lock_napi loop shouldn't have to mdelay. This patch adds an
      ixgbe_qv_disable along with a new IXGBE_QV_STATE_DISABLED bit, which it uses to
      indicate to the poll and napi routines that the q_vector has been disabled. Now
      the ixgbe_napi_disable_all function will wait until all pending work has been
      finished and prevent any future work from being started.
      Signed-off-by: NJacob Keller <jacob.e.keller@intel.com>
      Cc: Eliezer Tamir <eliezer.tamir@linux.intel.com>
      Cc: Alexander Duyck <alexander.duyck@intel.com>
      Cc: Hyong-Youb Kim <hykim@myri.com>
      Cc: Amir Vadai <amirv@mellanox.com>
      Cc: Dmitry Kravkov <dmitry@broadcom.com>
      Tested-by: NPhil Schmitt <phillip.j.schmitt@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      27d9ce4f
  27. 02 10月, 2013 1 次提交
  28. 25 9月, 2013 1 次提交
    • J
      intel: Remove extern from function prototypes · 5ccc921a
      Joe Perches 提交于
      There are a mix of function prototypes with and without extern
      in the kernel sources.  Standardize on not using extern for
      function prototypes.
      
      Function prototypes don't need to be written with extern.
      extern is assumed by the compiler.  Its use is as unnecessary as
      using auto to declare automatic/local variables in a block.
      Signed-off-by: NJoe Perches <joe@perches.com>
      5ccc921a
  29. 02 8月, 2013 1 次提交
  30. 31 7月, 2013 2 次提交