On 11/18/2014 11:50 PM, Or Gerlitz wrote:
On Tue, Nov 18, 2014 at 7:14 PM, Yishai Hadas
yish...@dev.mellanox.co.il wrote:
On 11/18/2014 4:42 PM, Or Gerlitz wrote:
Can we somehow make this patch generic (e.g land in the IB core) such
that it can apply also for mlx5 (and other HW drivers...)
On 11/19/2014 2:15 PM, Yishai Hadas wrote:
For that reason we believe that the correct place to use the zap call
is in the HW driver and not in IB core
OK let it be - get this one (after the trivial comments are addressed)
in and let the ones that follow see if they
can generalize/re-use
Implements the IB core disassociate_ucontext API. The driver detaches the HW
resources for a given user context to prevent a dependency between application
termination and device disconnecting. This is done by managing the VMAs that
were mapped to the HW bars such as door bell and blueflame. When
On 11/18/2014 8:42 AM, Or Gerlitz wrote:
On 11/18/2014 2:11 PM, Yishai Hadas wrote:
Implements the IB core disassociate_ucontext API. The driver detaches
the HW
resources for a given user context to prevent a dependency between
application
termination and device disconnecting. This is done by
On 11/18/2014 4:42 PM, Or Gerlitz wrote:
On 11/18/2014 2:11 PM, Yishai Hadas wrote:
Implements the IB core disassociate_ucontext API. The driver detaches
the HW
resources for a given user context to prevent a dependency between
application
termination and device disconnecting. This is done by
On Tue, Nov 18, 2014 at 7:14 PM, Yishai Hadas
yish...@dev.mellanox.co.il wrote:
On 11/18/2014 4:42 PM, Or Gerlitz wrote:
Can we somehow make this patch generic (e.g land in the IB core) such
that it can apply also for mlx5 (and other HW drivers...) basically, the
HW driver should tell the IB
