Hi, > -----Original Message----- > From: Jiawei(Jonny) Wang <jiaw...@nvidia.com> > Sent: Wednesday, October 27, 2021 1:35 PM > To: Slava Ovsiienko <viachesl...@nvidia.com>; Matan Azrad > <ma...@nvidia.com>; Ori Kam <or...@nvidia.com>; NBU-Contact-Thomas > Monjalon <tho...@monjalon.net> > Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com> > Subject: [PATCH v3] net/mlx5: optimize the device spawn time with > representors > > During the device spawn process, mlx5 PMD queried the available flow > priorities by calling mlx5_flow_discover_priorities, queried > if the DR drop action was supported on the root table by calling > the mlx5_flow_discover_dr_action_support routine, and queried the > availability of metadata register C by calling mlx5_flow_discover_mreg_c. > > These functions created the test flows to get the supported fields, and > at the end destroyed the test flows. The test flows in the first two > functions was created on the root table. > If the device was spawned with multiple representors, these test flows > were created and destroyed on each representor as well. The above > operations took a significant amount of init time during the device spawn. > > This patch optimizes the device discover functions, if there is > the device with multiple representors (VF/SF) being spawned, > the priority and drop action and metadata register support check can be > done only ones and check results can be shared for all representors. > > Signed-off-by: Jiawei Wang <jiaw...@nvidia.com> > Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com> > --- > v3: Rebase > v2: Fix the CI warning >
Removed v2 from next-net-mlx, And applied v3 to next-net-mlx, Kindest regards, Raslan Darawsheh
