tree 5a00fa66ad14cb5d3527f20ce91f7e87963ea2f8
parent 22d79c9a912c9d56258a0adf8a9c8cbfb6f2fd1a
author Jason Gunthorpe <jgg@mellanox.com> 1566213423 +0300
committer Jason Gunthorpe <jgg@mellanox.com> 1566407322 -0300

RDMA/odp: Make the three ways to create a umem_odp clear

The three paths to build the umem_odps are kind of muddled, they are:
- As a normal ib_mr umem
- As a child in an implicit ODP umem tree
- As the root of an implicit ODP umem tree

Only the first two are actually umem's, the last is an abuse.

The implicit case can only be triggered by explicit driver request, it
should never be co-mingled with the normal case. While we are here, make
sensible function names and add some comments to make this clearer.

Link: https://lore.kernel.org/r/20190819111710.18440-6-leon@kernel.org
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>