On 12/29/2015 5:24 PM, Or Gerlitz wrote:
On 12/29/2015 3:24 PM, Matan Barak wrote:
[...] We use a new firmware command in order to populate the GID table
and store the type along with the GID value.
Its a new value to existing command.. so better say we use a new value
to the SET_PORT firmwa
On 12/29/2015 3:24 PM, Matan Barak wrote:
[...] We use a new firmware command in order to populate the GID table and
store the type along with the GID value.
Its a new value to existing command.. so better say we use a new value
to the SET_PORT firmware command to do X
Also here, break out
In RoCE, GID table is managed in the IB core driver. The role of the
mlx4 driver is to synchronize the HW with the entries in the GID table.
Since it is possible that the same GID value will appear more than once
in the GID table (though with different attributes) it is required from
the mlx4 drive
