Displaying 7 results from an estimated 7 matches for "hfi".
Did you mean:
fi
2019 Nov 12
0
[PATCH v3 06/14] RDMA/hfi1: Use mmu_interval_notifier_insert for user_exp_rcv
...s of mmu_notifiers to use the new API.
The conversion is fairly straightforward, however the existing use of
notifiers here seems to be racey.
Tested-by: Dennis Dalessandro <dennis.dalessandro at intel.com>
Signed-off-by: Jason Gunthorpe <jgg at mellanox.com>
---
drivers/infiniband/hw/hfi1/file_ops.c | 2 +-
drivers/infiniband/hw/hfi1/hfi.h | 2 +-
drivers/infiniband/hw/hfi1/user_exp_rcv.c | 146 +++++++++-------------
drivers/infiniband/hw/hfi1/user_exp_rcv.h | 3 +-
4 files changed, 60 insertions(+), 93 deletions(-)
diff --git a/drivers/infiniband/hw/hfi1/file_...
2019 Oct 28
1
[PATCH v2 06/15] RDMA/hfi1: Use mmu_range_notifier_inset for user_exp_rcv
...n is fairly straightforward, however the existing use of
notifiers here seems to be racey.
Cc: Mike Marciniszyn <mike.marciniszyn at intel.com>
Cc: Dennis Dalessandro <dennis.dalessandro at intel.com>
Signed-off-by: Jason Gunthorpe <jgg at mellanox.com>
---
drivers/infiniband/hw/hfi1/file_ops.c | 2 +-
drivers/infiniband/hw/hfi1/hfi.h | 2 +-
drivers/infiniband/hw/hfi1/user_exp_rcv.c | 146 +++++++++-------------
drivers/infiniband/hw/hfi1/user_exp_rcv.h | 3 +-
4 files changed, 60 insertions(+), 93 deletions(-)
diff --git a/drivers/infiniband/hw/hfi1/file_...
2019 Nov 01
0
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
On 10/28/19 1:10 PM, Jason Gunthorpe wrote:
> From: Jason Gunthorpe <jgg at mellanox.com>
>
> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
> scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
> they only use invalidate_range_start/end and immediately check the
> invalidating range against some driver data structure to tell if the
> driver is interested. Half of them use an interval_tree, the others ar...
2019 Nov 12
20
[PATCH hmm v3 00/14] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others are
simple linear sear...
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others are
simple linear sear...
2018 Nov 25
6
RFC: Modernizing our use of auto
I'm not advocating AAA.
However this is a proposal for more modern thinking regarding the
permissiveness of auto in LLVM codebases.
Currently the rule on the use of auto is here:
https://llvm.org/docs/CodingStandards.html#use-auto-type-deduction-to-make-code-more-readable
It is quite strict. It allows the use of auto for
* lambdas
* iterators because they are long to type
* casts to
2009 Jul 23
1
[PATCH server] changes required for fedora rawhide inclusion.
...zlT2h+>&ZBN<a`39(lUTWL7$G~$m0PW{!rvt%-Zv))#VKrzjaUPPBHX^ls@&eVFoZc
zj)R1%a_i|FU}E$zDa&mi#dDh-&%kZDxPLZa5c=x1A&o*$?8><G=5bhU<~(a^apcwT
zKmD^-n+$1WPP6x}dvxEYa?7!qYr9hV7x=7oxoCon1v_)s#Ij{<@2&beIHB){y|*Ig
zd2f at ezW3IEn*ZsaxF%#sBY#3QGpWY9Im_XaF9-2T+WySmZW}SXzWohfiE*sU5B#!2
zyrjK9R}x1yb;q2bU>`9iS+1Y0OV?ID6sgjB3bhS5cY5{{&{?(CEB{3KMuGq>V5dzq
zB8DD6tB%dPZ>oRIp7&8OAU{hr*nh$U4}=*GN**nK*yno<>~2f;DS?c>T(HOhx^=Pf
zwe7o(dgipu8T$J<GLPf{^NgMNy+%nA2SYyW`=HpxIWvGU(3g_3^&2oHFE$2<ZUE6#
zWS2bGNGRnVdB=Y|fEbQx9Yefa_h2Sk2W_y(WCl}@a6ywK0F9|p&a...