1. 15 5月, 2007 3 次提交
  2. 07 5月, 2007 1 次提交
    • M
      IB: Add CQ comp_vector support · f4fd0b22
      Michael S. Tsirkin 提交于
      Add a num_comp_vectors member to struct ib_device and extend
      ib_create_cq() to pass in a comp_vector parameter -- this parallels
      the userspace libibverbs API.  Update all hardware drivers to set
      num_comp_vectors to 1 and have all ULPs pass 0 for the comp_vector
      value.  Pass the value of num_comp_vectors to userspace rather than
      hard-coding a value of 1.
      
      We want multiple CQ event vector support (via MSI-X or similar for
      adapters that can generate multiple interrupts), but it's not clear
      how many vectors we want, or how we want to deal with policy issues
      such as how to decide which vector to use or how to set up interrupt
      affinity.  This patch is useful for experimenting, since no core
      changes will be necessary when updating a driver to support multiple
      vectors, and we know that we want to make at least these changes
      anyway.
      Signed-off-by: NMichael S. Tsirkin <mst@dev.mellanox.co.il>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      f4fd0b22
  3. 02 5月, 2007 1 次提交
  4. 26 4月, 2007 1 次提交
  5. 25 4月, 2007 1 次提交
  6. 13 4月, 2007 2 次提交
  7. 02 3月, 2007 1 次提交
    • H
      IB/ehca: Fix sync between completion handler and destroy cq · 31726798
      Hoang-Nam Nguyen 提交于
      This patch fixes two issues reported by Roland Dreier and Christoph Hellwig:
      
      - Mismatched sync/locking between completion handler and destroy cq We
        introduced a counter nr_events per cq to track number of irq events
        seen. This counter is incremented when an event queue entry is seen
        and decremented after completion handler has been called regardless
        if scaling code is active or not. Note that nr_callbacks tracks
        number of events assigned to a cpu and both counters can potentially
        diverge.
      
        The sync between running completion handler and destroy cq is done
        by using the global spin lock ehca_cq_idr_lock.
      
      - Replace yield by wait_event on the counter above to become zero.
      Signed-off-by: NHoang-Nam Nguyen <hnguyen@de.ibm.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      31726798
  8. 17 2月, 2007 2 次提交
  9. 05 2月, 2007 1 次提交
  10. 10 1月, 2007 1 次提交
    • H
      IB/ehca: Use proper GFP_ flags for get_zeroed_page() · f2d91361
      Hoang-Nam Nguyen 提交于
      Here is a patch for ehca to use proper flag, ie. GFP_ATOMIC
      resp. GFP_KERNEL, when calling get_zeroed_page() to prevent "Bug:
      scheduling while atomic...". This error does not cause a kernel panic
      but makes ipoib un-usable afterwards.  It is reproducible on
      2.6.20-rc4 if one does ifconfig down during a flood ping test.  I have
      not observed this error in earlier releases incl. 2.6.20-rc1.
      
      This error occurs when a qp event/irq is received and ehca event
      handler allocates a control block/page to obtain HCA error data block.
      Use of GFP_ATOMIC when in interrupt context prevents this issue.
      
      Signed-off-by Hoang-Nam Nguyen <hnguyen@de.ibm.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      f2d91361
  11. 08 12月, 2006 1 次提交
  12. 30 11月, 2006 1 次提交
  13. 10 11月, 2006 1 次提交
  14. 03 10月, 2006 1 次提交
  15. 23 9月, 2006 2 次提交