summaryrefslogtreecommitdiff
path: root/drivers/net/mlx4/mlx4_flow.c
diff options
context:
space:
mode:
authorYongseok Koh <yskoh@mellanox.com>2019-04-01 14:12:55 -0700
committerFerruh Yigit <ferruh.yigit@intel.com>2019-04-05 17:45:22 +0200
commit7be600c8d8ef48cbd4b73077923821798190f2f1 (patch)
tree7ab465a93a432a2607afe11f8c431f4850616810 /drivers/net/mlx4/mlx4_flow.c
parent9a8ab29b84d3479512855fdd849679921ef4567a (diff)
downloaddpdk-7be600c8d8ef48cbd4b73077923821798190f2f1.zip
dpdk-7be600c8d8ef48cbd4b73077923821798190f2f1.tar.gz
dpdk-7be600c8d8ef48cbd4b73077923821798190f2f1.tar.xz
net/mlx5: rework PMD global data init
There's more need to have PMD global data structure. This should be initialized once per a process regardless of how many PMD instances are probed. mlx5_init_once() is called during probing and make sure all the init functions are called once per a process. Currently, such global data and its initialization functions are even scattered. Rather than 'extern'-ing such variables and calling such functions one by one making sure it is called only once by checking the validity of such variables, it will be better to have a global storage to hold such data and a consolidated function having all the initializations. The existing shared memory gets more extensively used for this purpose. As there could be multiple secondary processes, a static storage (local to process) is also added. As the reserved virtual address for UAR remap is a PMD global resource, this doesn't need to be stored in the device priv structure, but in the PMD global data. Signed-off-by: Yongseok Koh <yskoh@mellanox.com> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Diffstat (limited to 'drivers/net/mlx4/mlx4_flow.c')
0 files changed, 0 insertions, 0 deletions