1. 12 Jan, 2011 1 commit
    • Aleksey Senin's avatar
      IB/mlx4: Handle protocol field in multicast table · da995a8a
      Aleksey Senin authored
      The newest device firmware stores IB vs. Ethernet protocol in two bits
      in members_count field of multicast group table (0: Infiniband, 1:
      Ethernet).  When changing the QP members count for a multicast group,
      it important not to reset this information.  When calling multicast
      attach first time, the protocol type should be specified.  In this
      patch we always set it IB, but in the future we will handle Ethernet
      too.  When looking for a QP, the protocol type shoud be checked too.
      Signed-off-by: default avatarAleksey Senin <alekseys@voltaire.com>
      Signed-off-by: default avatarRoland Dreier <rolandd@cisco.com>
      da995a8a
  2. 25 Oct, 2010 1 commit
    • Eli Cohen's avatar
      mlx4_core: Allow protocol drivers to find corresponding interfaces · 33c87f0a
      Eli Cohen authored
      Add a mechanism for mlx4 protocol drivers to get a pointer to other
      drivers's device objects.  For this, an exported function,
      mlx4_get_protocol_dev() is added, which allows a driver to get some
      other driver's device based on the protocol that the driver
      implements.  Two protocols are added: MLX4_PROTOCOL_IB and
      MLX4_PROTOCOL_EN.
      
      This will be used in mlx4 IBoE support so that mlx4_ib can find the
      corresponding mlx4_en netdev.
      Signed-off-by: default avatarEli Cohen <eli@mellanox.co.il>
      
      [ Clean up and rename a few things.  - Roland ]
      Signed-off-by: default avatarRoland Dreier <rolandd@cisco.com>
      33c87f0a
  3. 16 Apr, 2008 1 commit
    • Roland Dreier's avatar
      mlx4_core: Fix confusion between mlx4_event and mlx4_dev_event enums · 37608eea
      Roland Dreier authored
      The struct mlx4_interface.event() method was supposed to get an enum
      mlx4_dev_event, but the driver code was actually passing in the
      hardware enum mlx4_event values.  Fix up the callers of
      mlx4_dispatch_event() so that they pass in the right type of value,
      and fix up the event method in mlx4_ib so that it can handle the enum
      mlx4_dev_event values.
      
      This eliminates the need for the subtype parameter to the event
      method, so remove it.
      
      This also fixes the sparse warning
      
          drivers/net/mlx4/intf.c:127:48: warning: mixing different enum types
          drivers/net/mlx4/intf.c:127:48:     int enum mlx4_event  versus
          drivers/net/mlx4/intf.c:127:48:     int enum mlx4_dev_event
      Signed-off-by: default avatarRoland Dreier <rolandd@cisco.com>
      37608eea
  4. 08 May, 2007 1 commit
    • Roland Dreier's avatar
      IB/mlx4: Add a driver Mellanox ConnectX InfiniBand adapters · 225c7b1f
      Roland Dreier authored
      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: default avatarRoland Dreier <rolandd@cisco.com>
      225c7b1f
  5. 26 Aug, 2005 2 commits
  6. 16 Apr, 2005 2 commits
    • Michael S. Tsirkin's avatar
      [PATCH] IB/mthca: add fast memory region implementation · e0f5fdca
      Michael S. Tsirkin authored
      Implement fast memory regions (FMRs), where the driver writes directly into
      the HCA's translation tables rather than requiring a firmware command.  For
      Tavor, MTTs for FMR are separate from regular MTTs, and are reserved at driver
      initialization.  This is done to limit the amount of virtual memory needed to
      map the MTTs.  For Arbel, there's no such limitation, and all MTTs and MPTs
      may be used for FMR or for regular MR.
      Signed-off-by: default avatarMichael S. Tsirkin <mst@mellanox.co.il>
      Signed-off-by: default avatarRoland Dreier <roland@topspin.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      e0f5fdca
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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