1. 12 9月, 2013 1 次提交
    • M
      bnx2x: avoid atomic allocations during initialization · 996dedba
      Michal Schmidt 提交于
      During initialization bnx2x allocates significant amounts of memory
      (for rx data, rx SGEs, TPA pool) using atomic allocations.
      
      I received a report where bnx2x failed to allocate SGEs and it had
      to fall back to TPA-less operation.
      
      Let's use GFP_KERNEL allocations during initialization, which runs
      in process context. Add gfp_t parameters to functions that are used
      both in initialization and in the receive path.
      
      Use an unlikely branch in bnx2x_frag_alloc() to avoid atomic allocation
      by netdev_alloc_frag(). The branch is taken several thousands of times
      during initialization, but then never more. Note that fp->rx_frag_size
      is never greater than PAGE_SIZE, so __get_free_page() can be used here.
      Signed-off-by: NMichal Schmidt <mschmidt@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      996dedba
  2. 06 9月, 2013 2 次提交
  3. 28 8月, 2013 2 次提交
  4. 02 8月, 2013 2 次提交
    • Y
      bnx2x: Revising locking scheme for MAC configuration · 8b09be5f
      Yuval Mintz 提交于
      On very rare occasions, repeated load/unload stress test in the presence of
      our storage driver (bnx2i/bnx2fc) causes a kernel panic in bnx2x code
      (NULL pointer dereference). Stack traces indicate the issue happens during MAC
      configuration; thorough code review showed that indeed several races exist
      in which one thread can iterate over the list of configured MACs while another
      deletes entries from the same list.
      
      This patch adds a varient on the single-writer/Multiple-reader lock mechanism -
      It utilizes an already exsiting bottom-half lock, using it so that Whenever
      a writer is unable to continue due to the existence of another writer/reader,
      it pends its request for future deliverance.
      The writer / last readers will check for the existence of such requests and
      perform them instead of the original initiator.
      This prevents the writer from having to sleep while waiting for the lock
      to be accessible, which might cause deadlocks given the locks already
      held by the writer.
      
      Another result of this patch is that setting of Rx Mode is now made in
      sleepable context - Setting of Rx Mode is made under a bottom-half lock, which
      was always nontrivial for the bnx2x driver, as the HW/FW configuration requires
      wait for completions.
      Since sleep was impossible (due to the sleepless-context), various mechanisms
      were utilized to prevent the calling thread from sleep, but the truth was that
      when the caller thread (i.e, the one calling ndo_set_rx_mode()) returned, the
      Rx mode was still not set in HW/FW.
      
      bnx2x_set_rx_mode() will now overtly schedule for the Rx changes to be
      configured by the sp_rtnl_task which hold the RTNL lock and is sleepable
      context.
      Signed-off-by: NYuval Mintz <yuvalmin@broadcom.com>
      Signed-off-by: NAriel Elior <ariele@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8b09be5f
    • C
      net: rename CONFIG_NET_LL_RX_POLL to CONFIG_NET_RX_BUSY_POLL · e0d1095a
      Cong Wang 提交于
      Eliezer renames several *ll_poll to *busy_poll, but forgets
      CONFIG_NET_LL_RX_POLL, so in case of confusion, rename it too.
      
      Cc: Eliezer Tamir <eliezer.tamir@linux.intel.com>
      Cc: David S. Miller <davem@davemloft.net>
      Signed-off-by: NCong Wang <amwang@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e0d1095a
  5. 12 7月, 2013 1 次提交
  6. 11 7月, 2013 2 次提交
  7. 25 6月, 2013 1 次提交
  8. 24 6月, 2013 1 次提交
  9. 20 6月, 2013 2 次提交
  10. 05 6月, 2013 2 次提交
  11. 03 6月, 2013 3 次提交
  12. 02 6月, 2013 1 次提交
  13. 24 5月, 2013 1 次提交
  14. 20 5月, 2013 2 次提交
  15. 30 4月, 2013 1 次提交
  16. 25 4月, 2013 4 次提交
  17. 20 4月, 2013 1 次提交
  18. 19 4月, 2013 1 次提交
  19. 22 3月, 2013 1 次提交
  20. 21 3月, 2013 1 次提交
  21. 19 3月, 2013 1 次提交
  22. 18 3月, 2013 1 次提交
  23. 12 3月, 2013 2 次提交
  24. 28 2月, 2013 1 次提交
  25. 11 2月, 2013 1 次提交
  26. 24 1月, 2013 2 次提交