On 7/12/2018 11:53 PM, Or Gerlitz wrote:
On Wed, Jul 11, 2018 at 2:10 PM, Leon Romanovsky <leon@xxxxxxxxxx> wrote:
From: Yishai Hadas <yishaih@xxxxxxxxxxxx>
Use the PRM size including the reserved when working with the FTE
match data.
is this actually a bug fix?
No, it's some requirement from the new API to enable forward compatible
support without changing the kernel code.
Also drop some driver checks around the match criteria leaving the work
for firmware to enable forward compatibility for future bits there.
not following,
Same as for the 'reserved' field but also for extending the 'match
criteria' field with new bits without changing the kernel.
OTOH, suppose today we check that one of four bits is set and now one
added bit #5 and the
kernel doesn't check it, what removing the existing four checks buys you?
The idea was to have one place for those checking (i.e. firmware)
instead of splitting between legacy to new bits. (i.e. driver vs firmware).
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
