1. 19 6月, 2018 2 次提交
    • P
      RDMA: Use GID from the ib_gid_attr during the add_gid() callback · f4df9a7c
      Parav Pandit 提交于
      Now that ib_gid_attr contains the GID, make use of that in the add_gid()
      callback functions for the provider drivers to simplify the add_gid()
      implementations.
      Signed-off-by: NParav Pandit <parav@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leonro@mellanox.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      f4df9a7c
    • P
      IB/core: Introduce GID entry reference counts · b150c386
      Parav Pandit 提交于
      In order to be able to expose pointers to the ib_gid_attrs in the GID
      table we need to make it so the value of the pointer cannot be
      changed. Thus each GID table entry gets a unique piece of kref'd memory
      that is written only during initialization and remains constant for its
      lifetime.
      
      This eventually will allow the struct ib_gid_attrs to be returned without
      copy from many of query the APIs, but it also provides a way to track when
      all users of a HW table index go away.
      
      For roce we no longer allow an in-use HW table index to be re-used for a
      new an different entry. When a GID table entry needs to be removed it is
      hidden from the find API, but remains as a valid HW index and all
      ib_gid_attr points remain valid. The HW index is not relased until all
      users put the kref.
      
      Later patches will broadly replace the use of the sgid_index integer with
      the kref'd structure.
      
      Ultimately this will prevent security problems where the OS changes the
      properties of a HW GID table entry while an active user object is still
      using the entry.
      Signed-off-by: NParav Pandit <parav@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leonro@mellanox.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      b150c386
  2. 18 6月, 2018 2 次提交
  3. 16 6月, 2018 14 次提交
  4. 15 6月, 2018 11 次提交
  5. 14 6月, 2018 11 次提交