Thread (5 messages) 5 messages, 3 authors, 2019-05-03

Re: [PATCH v13 16/20] IB/mlx4, arm64: untag user pointers in mlx4_get_umem_mr

From: Jason Gunthorpe <jgg@ziepe.ca>
Date: 2019-05-02 18:44:46
Also in: linux-arch, linux-arm-kernel, linux-mm, linux-rdma, lkml

Possibly related (same subject, not in this thread)

On Tue, Apr 30, 2019 at 12:16:25PM +0100, Catalin Marinas wrote:
quoted
Interesting, the followup question is why mlx4 is only one driver in IB which
needs such code in umem_mr. I'll take a look on it.
I don't know. Just using the light heuristics of find_vma() shows some
other places. For example, ib_umem_odp_get() gets the umem->address via
ib_umem_start(). This was previously set in ib_umem_get() as called from
mlx4_get_umem_mr(). Should the above patch have just untagged "start" on
entry?
I have a feeling that there needs to be something for this in the odp
code..

Presumably mmu notifiers and what not also use untagged pointers? Most
likely then the umem should also be storing untagged pointers.

This probably becomes problematic because we do want the tag in cases
talking about the base VA of the MR..

Jason
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help