[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5475E19D.5000508@mellanox.com>
Date: Wed, 26 Nov 2014 16:20:13 +0200
From: Or Gerlitz <ogerlitz@...lanox.com>
To: David Miller <davem@...emloft.net>
CC: <netdev@...r.kernel.org>, <matanb@...lanox.com>,
<amirv@...lanox.com>, <jackm@....mellanox.co.il>
Subject: Re: [PATCH net] net/mlx4_core: Limit count field to 24 bits in qp_alloc_res
On 11/25/2014 9:16 PM, David Miller wrote:
> From: Or Gerlitz <ogerlitz@...lanox.com>
> Date: Tue, 25 Nov 2014 11:54:31 +0200
>
>> case RES_OP_RESERVE:
>> - count = get_param_l(&in_param);
>> + count = get_param_l(&in_param) & 0xffffff;
> I think if these high bits are set, you should be using the maximum
> value rather then truncating.
Dave,
To make it clear (maybe the change-log wasn't explaining it well
enough), the 32 bits in_param are
divided to 24 bits of count and 8 bits for optimized allocation scheme
which isn't yet supported
by the Linux PF driver.
Currently, the upstream PF driver is wrongly NOT masking out these eight
bits and as such, some
VF drivers which are already setting them for optimized allocation are
failing to allocate QPs as
the count seen by the PF becomes way too large. The optimization is
best effort anyway, and hence
we can safely ignore their request.
If we follow your suggestion and allocate to these VFs per the maximum
number, we will
hit their quota after they open one QP and their over-all bring up will
fail, so this will not help.
Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists