[dpdk-stable] [PATCH v2 3/3] [18.11] net/mlx4: remove device register remap

[Kevin Traynor]

On 08/07/2020 10:28, Ali Alnubani wrote:
>> -----Original Message-----
>> From: stable <stable-bounces at dpdk.org> On Behalf Of Viacheslav Ovsiienko
>> Sent: Tuesday, July 7, 2020 10:13 AM
>> To: stable at dpdk.org
>> Cc: ktraynor at redhat.com; Yongseok Koh <yskoh at mellanox.com>
>> Subject: [dpdk-stable] [PATCH v2 3/3] [18.11] net/mlx4: remove device
>> register remap
>>
>> From: Yongseok Koh <yskoh at mellanox.com>
>>
>> UAR (User Access Region) register does not need to be remapped for
>> primary process but it should be remapped only for secondary process.
>> UAR register table is in the process private structure in rte_eth_devices[],
>> (struct mlx4_proc_priv *)rte_eth_devices[port_id].process_private
>>
>> The actual UAR table follows the data structure and the table is used for both
>> Tx and Rx.
>>
>> For Tx, BlueFlame in UAR is used to ring the doorbell.
>> MLX4_TX_BFREG(txq) is defined to get a register for the txq. Processes
>> access its own private data to acquire the register from the UAR table.
>>
>> For Rx, the doorbell in UAR is required in arming CQ event. However, it is a
>> known issue that the register isn't remapped for secondary process.
>>
>> Signed-off-by: Yongseok Koh <yskoh at mellanox.com>
>> Signed-off-by: Viacheslav Ovsiienko <viacheslavo at mellanox.com>
>> Acked-by: Shahaf Shuler <shahafs at mellanox.com>
> 
> Tested-by: Ali Alnubani <alialnu at mellanox.com>
> 

Applied, thanks Slava and Ali (and Yongseok o/)