On Mon, Aug 19, 2019 at 02:16:58PM +0300, Leon Romanovsky wrote: > From: Leon Romanovsky <leonro@xxxxxxxxxxxx> > > Hi, > > This series from Jason is a collection of general cleanups for > ODP to clarify some of the flows around umem creation and use > of the interval tree. > > It is based on patch "RDMA/mlx5: Fix MR npages calculation for > IB_ACCESS_HUGETLB" > https://lore.kernel.org/linux-rdma/20190815083834.9245-5-leon@xxxxxxxxxx > > Thanks > > Jason Gunthorpe (11): > RDMA/odp: Use the common interval tree library instead of generic > RDMA/odp: Iterate over the whole rbtree directly > RDMA/odp: Make it clearer when a umem is an implicit ODP umem > RMDA/odp: Consolidate umem_odp initialization > RDMA/odp: Make the three ways to create a umem_odp clear > RDMA/odp: Split creating a umem_odp from ib_umem_get > RDMA/odp: Provide ib_umem_odp_release() to undo the allocs > RDMA/odp: Check for overflow when computing the umem_odp end > RDMA/odp: Use kvcalloc for the dma_list and page_list > RDMA/mlx5: Use ib_umem_start instead of umem.address > RDMA/mlx5: Use odp instead of mr->umem in pagefault_mr > > Moni Shoua (1): > RDMA/core: Make invalidate_range a device operation Applied to for-next, thanks Jason
