From: Or Gerlitz <ogerlitz@mellanox.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <matanb@mellanox.com>,
<amirv@mellanox.com>, <jackm@dev.mellanox.co.il>
Subject: Re: [PATCH net] net/mlx4_core: Limit count field to 24 bits in qp_alloc_res
Date: Wed, 26 Nov 2014 16:20:13 +0200 [thread overview]
Message-ID: <5475E19D.5000508@mellanox.com> (raw)
In-Reply-To: <20141125.141620.1331667846639491375.davem@davemloft.net>
On 11/25/2014 9:16 PM, David Miller wrote:
> From: Or Gerlitz <ogerlitz@mellanox.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.
next prev parent reply other threads:[~2014-11-26 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 9:54 [PATCH net] net/mlx4_core: Limit count field to 24 bits in qp_alloc_res Or Gerlitz
2014-11-25 19:16 ` David Miller
2014-11-26 14:20 ` Or Gerlitz [this message]
2014-11-26 17:05 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5475E19D.5000508@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=jackm@dev.mellanox.co.il \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.