1. 21 5月, 2011 1 次提交
  2. 18 10月, 2010 1 次提交
  3. 24 5月, 2010 1 次提交
  4. 22 4月, 2010 1 次提交
  5. 04 3月, 2010 1 次提交
  6. 25 2月, 2010 1 次提交
  7. 30 12月, 2008 1 次提交
    • R
      RDMA/addr: Fix build breakage when IPv6 is disabled · 2c4ab624
      Roland Dreier 提交于
      Commit 38617c64 ("RDMA/addr: Add support for translating IPv6
      addresses") broke the build when CONFIG_IPV6=n, because the ib_addr
      module unconditionally attempted to call ipv6_chk_addr() and other
      IPv6 functions that are not defined when IPv6 is disabled.  Fix this
      by only building IPv6 support if CONFIG_IPV6 is turned on, and
      add a Kconfig dependency to prevent the ib_addr code from being built
      in when IPv6 is built modular.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      2c4ab624
  8. 05 2月, 2008 1 次提交
  9. 10 7月, 2007 1 次提交
  10. 10 5月, 2007 1 次提交
  11. 09 5月, 2007 2 次提交
    • R
      IB/mlx4: Add a driver Mellanox ConnectX InfiniBand adapters · 225c7b1f
      Roland Dreier 提交于
      Add an InfiniBand driver for Mellanox ConnectX adapters.  Because
      these adapters can also be used as ethernet NICs and Fibre Channel 
      HBAs, the driver is split into two modules: 
       
        mlx4_core: Handles low-level things like device initialization and 
          processing firmware commands.  Also controls resource allocation 
          so that the InfiniBand, ethernet and FC functions can share a 
          device without stepping on each other. 
       
        mlx4_ib: Handles InfiniBand-specific things; plugs into the 
          InfiniBand midlayer. 
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      225c7b1f
    • R
      IB/uverbs: Export ib_umem_get()/ib_umem_release() to modules · f7c6a7b5
      Roland Dreier 提交于
      Export ib_umem_get()/ib_umem_release() and put low-level drivers in
      control of when to call ib_umem_get() to pin and DMA map userspace,
      rather than always calling it in ib_uverbs_reg_mr() before calling the
      low-level driver's reg_user_mr method.
      
      Also move these functions to be in the ib_core module instead of
      ib_uverbs, so that driver modules using them do not depend on
      ib_uverbs.
      
      This has a number of advantages:
       - It is better design from the standpoint of making generic code a
         library that can be used or overridden by device-specific code as
         the details of specific devices dictate.
       - Drivers that do not need to pin userspace memory regions do not
         need to take the performance hit of calling ib_mem_get().  For
         example, although I have not tried to implement it in this patch,
         the ipath driver should be able to avoid pinning memory and just
         use copy_{to,from}_user() to access userspace memory regions.
       - Buffers that need special mapping treatment can be identified by
         the low-level driver.  For example, it may be possible to solve
         some Altix-specific memory ordering issues with mthca CQs in
         userspace by mapping CQ buffers with extra flags.
       - Drivers that need to pin and DMA map userspace memory for things
         other than memory regions can use ib_umem_get() directly, instead
         of hacks using extra parameters to their reg_phys_mr method.  For
         example, the mlx4 driver that is pending being merged needs to pin
         and DMA map QP and CQ buffers, but it does not need to create a
         memory key for these buffers.  So the cleanest solution is for mlx4
         to call ib_umem_get() in the create_qp and create_cq methods.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      f7c6a7b5
  12. 13 2月, 2007 1 次提交
  13. 23 9月, 2006 3 次提交
  14. 22 6月, 2006 1 次提交
  15. 18 6月, 2006 1 次提交
  16. 01 4月, 2006 1 次提交
  17. 03 11月, 2005 1 次提交
  18. 08 9月, 2005 1 次提交
  19. 24 8月, 2005 1 次提交
  20. 08 7月, 2005 1 次提交
  21. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4