> On 6 Feb 2019, at 19:02, jackm wrote:
>
> On Wed, 6 Feb 2019 16:40:14 +0100
> Håkon Bugge wrote:
>
>> Jack,
>>
>> A major contributor to the long processing time in the PF driver
>> proxying QP1 packets is:
>>
>> create_pv_resources
>> -> ib_create_cq(ctx->ib_dev, mlx4_ib_tunnel_comp_h
On Wed, 6 Feb 2019 16:40:14 +0100
Håkon Bugge wrote:
> Jack,
>
> A major contributor to the long processing time in the PF driver
> proxying QP1 packets is:
>
> create_pv_resources
>-> ib_create_cq(ctx->ib_dev, mlx4_ib_tunnel_comp_handler,
>NULL, ctx, cq_si
> On 6 Feb 2019, at 09:50, Håkon Bugge wrote:
>
>
>
>> On 5 Feb 2019, at 23:36, Jason Gunthorpe wrote:
>>
>> On Thu, Jan 31, 2019 at 06:09:51PM +0100, Håkon Bugge wrote:
>>> Using CX-3 virtual functions, either from a bare-metal machine or
>>> pass-through from a VM, MAD packets are proxie
> On 5 Feb 2019, at 23:36, Jason Gunthorpe wrote:
>
> On Thu, Jan 31, 2019 at 06:09:51PM +0100, Håkon Bugge wrote:
>> Using CX-3 virtual functions, either from a bare-metal machine or
>> pass-through from a VM, MAD packets are proxied through the PF driver.
>>
>> Since the VMs have separate n
On Thu, Jan 31, 2019 at 06:09:51PM +0100, Håkon Bugge wrote:
> Using CX-3 virtual functions, either from a bare-metal machine or
> pass-through from a VM, MAD packets are proxied through the PF driver.
>
> Since the VMs have separate name spaces for MAD Transaction Ids
> (TIDs), the PF driver has
Using CX-3 virtual functions, either from a bare-metal machine or
pass-through from a VM, MAD packets are proxied through the PF driver.
Since the VMs have separate name spaces for MAD Transaction Ids
(TIDs), the PF driver has to re-map the TIDs and keep the book keeping
in a cache.
Following the
