common/mlx5: fix CPU detection for PCI relaxed ordering
PATCH 1/1 common/mlx5: fix CPU detection for PCI relaxed ordering
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD
because it was not exported as part of the .map file.
It is fixed by exporting a function, which is cleaner than a variable.
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Note: the priority of the constructor was probably irrelevant.
At the same time, the comments are reworded or dropped if useless.
--- drivers/common/mlx5/linux/mlx5_common_verbs.c | 2 +- drivers/common/mlx5/mlx5_common.c | 53 ++++++++----------- drivers/common/mlx5/mlx5_common.h | 4 +- .../common/mlx5/rte_common_mlx5_version.map | 2 + drivers/net/mlx5/mlx5_flow_dv.c | 2 +- 5 files changed, 28 insertions(+), 35 deletions(-)
drivers/common/mlx5/linux/mlx5_common_verbs.c +1 -1
@@ -55,7 +55,7 @@ mlx5_common_verbs_reg_mr(void *pd, void *addr, size_t length,memset (pmd_mr,0 ,sizeof (*pmd_mr)); ibv_mr = mlx5_glue->reg_mr (pd, addr, length,IBV_ACCESS_LOCAL_WRITE | - (haswell_broadwell_cpu ?0 : + (mlx5_cpu_is_haswell_broadwell () ?0 :IBV_ACCESS_RELAXED_ORDERING ));if (!ibv_mr)return -1 ;
drivers/common/mlx5/mlx5_common.c +21 -32
91 lines not on this page · raw message
drivers/common/mlx5/mlx5_common.h +3 -1
@@ -243,6 +243,9 @@ struct mlx5_klm {LIST_HEAD (mlx5_dbr_page_list, mlx5_devx_dbr_page); +__rte_internal +bool mlx5_cpu_is_haswell_broadwell(void); +__rte_internal enum mlx5_class mlx5_class_get(struct rte_devargs *devargs); __rte_internal
@@ -255,6 +258,5 @@ int64_t mlx5_get_dbr(void *ctx, struct mlx5_dbr_page_list *head,__rte_internal int32_t mlx5_release_dbr(struct mlx5_dbr_page_list *head, uint32_t umem_id,uint64_t offset); -extern uint8_t haswell_broadwell_cpu;#endif /* RTE_PMD_MLX5_COMMON_H_ */
drivers/common/mlx5/rte_common_mlx5_version.map +2 -0
@@ -6,6 +6,8 @@ INTERNAL { mlx5_common_verbs_reg_mr; mlx5_common_verbs_dereg_mr; + mlx5_cpu_is_haswell_broadwell; + mlx5_create_mr_ext; mlx5_dev_to_pci_addr;
drivers/net/mlx5/mlx5_flow_dv.c +1 -1
@@ -4201,7 +4201,7 @@ flow_dv_create_counter_stat_mem_mng(struct rte_eth_dev *dev, int raws_n) mkey_attr.klm_num =0 ;if (priv->config.hca_attr.relaxed_ordering_write && priv->config.hca_attr.relaxed_ordering_read && - !haswell_broadwell_cpu) + !mlx5_cpu_is_haswell_broadwell ()) mkey_attr.relaxed_ordering =1 ; mem_mng->dm =mlx5_devx_cmd_mkey_create (sh->ctx, &mkey_attr);if (!mem_mng->dm) {
Signature · 1 line
2.27.0
Quoted 22 lines
-----Original Message-----
From: Thomas Monjalon <[email protected]>
Sent: Sunday, July 19, 2020 13:08
To: [email protected]
Cc: Raslan Darawsheh <[email protected]>; Shiri Kuzin <[email protected]>; [email protected]; Matan Azrad <[email protected]>; Shahaf Shuler <[email protected]>; Slava Ovsiienko <[email protected]>; Ray Kinsella <[email protected]>; Neil Horman <[email protected]>
Subject: [PATCH] common/mlx5: fix CPU detection for PCI relaxed orderingThe detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
It is fixed by exporting a function, which is cleaner than a variable.By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Note: the priority of the constructor was probably irrelevant.
Quoted 8 lines
At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering in unsuitableCPUs")
Cc: [email protected]
Cc: [email protected]Signed-off-by Thomas Monjalon <[email protected]>
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example - rte_eth_devices.
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once and doesn't depend in any parameter.
Quoted 188 lines
Note: the priority of the constructor was probably irrelevant.
At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering in unsuitableCPUs")
Cc: [email protected]
Cc: [email protected]Signed-off-by Thomas Monjalon <[email protected]>--- drivers/common/mlx5/linux/mlx5_common_verbs.c | 2 +- drivers/common/mlx5/mlx5_common.c | 53 ++++++++----------- drivers/common/mlx5/mlx5_common.h | 4 +- .../common/mlx5/rte_common_mlx5_version.map | 2 + drivers/net/mlx5/mlx5_flow_dv.c | 2 +- 5 files changed, 28 insertions(+), 35 deletions(-)drivers/common/mlx5/linux/mlx5_common_verbs.c +1
-1@@ -55,7 +55,7 @@ mlx5_common_verbs_reg_mr(void *pd, void *addr,size_t length, memset(pmd_mr, 0, sizeof(*pmd_mr)); ibv_mr = mlx5_glue->reg_mr (pd, addr, length,IBV_ACCESS_LOCAL_WRITE | - (haswell_broadwell_cpu ?0 : + (mlx5_cpu_is_haswell_broadwell () ?0 :IBV_ACCESS_RELAXED_ORDERING ));if (!ibv_mr)drivers/common/mlx5/linux/mlx5_common_verbs.c +0
-0return -1 ;drivers/common/mlx5/mlx5_common.c +2
-14@@ -20,8 +20,6 @@ int mlx5_common_logtype; const struct mlx5_glue *mlx5_glue;#endif -uint8_t haswell_broadwell_cpu; -static int mlx5_class_check_handler(__rte_unused const char *key, const char *value,void *opaque)@@ -59,19 +57,8 @@ mlx5_class_get(struct rte_devargs *devargs) } -/* In case this is an x86_64 intel processor to check if -* we should use relaxed ordering. -*/ #ifdef RTE_ARCH_X86_64 -/** -* This function returns processor identification and feature information -* into the registers. -* -* @param eax, ebx, ecx, edx -* Pointers to the registers that will hold cpu information. -* @param level -* The main category of information returned. -*/ +/* Processor identification and feature information filled in +registers. */ static inline void mlx5_cpu_id (unsigned int level,unsigned int *eax,unsigned int *ebx, unsigned int *ecx, unsigned int *edx) @@ -97,17 +84,7 @@
RTE_INIT_PRIO(mlx5_glue_init, CLASS)drivers/common/mlx5/mlx5_common.c +1
-11mlx5_glue_constructor (); } -/** -* This function is responsible of initializing the variable -* haswell_broadwell_cpu by checking if the cpu is intel -* and reading the data returned from mlx5_cpu_id(). -* since haswell and broadwell cpus don't have improved performance -* when using relaxed ordering we want to check the cpu type before -* before deciding whether to enable RO or not. -* if the cpu is haswell or broadwell the variable will be set to 1 -* otherwise it will be 0. -*/ -RTE_INIT_PRIO(mlx5_is_haswell_broadwell_cpu, LOG) +static bool mlx5_x86_is_haswell_broadwell (void ) {#ifdef RTE_ARCH_X86_64 unsigned int broadwell_models[4] = {0x3d, 0x47, 0x4F, 0x56}; @@ -125,8 +102,7 @@
RTE_INIT_PRIO(mlx5_is_haswell_broadwell_cpu, LOG)drivers/common/mlx5/mlx5_common.c +9
-7vendor = ebx; max_level = eax;if (max_level <1 ) { - haswell_broadwell_cpu =0 ; -return ; +return false; }mlx5_cpu_id (1 , &eax, &ebx, &ecx, &edx); model = (eax >>4 ) &0x0f ;@@ -140,18 +116,31 @@ RTE_INIT_PRIO(mlx5_is_haswell_broadwell_cpu, LOG)if (brand_id ==0 && family ==0x6 ) {for (i =0 ; i <RTE_DIM (broadwell_models); i++)if (model == broadwell_models[i]) { - haswell_broadwell_cpu =1 ; -return ; +return true; }for (i =0 ; i <RTE_DIM (haswell_models); i++)if (model == haswell_models[i]) { - haswell_broadwell_cpu =1 ; -return ; +return true; } } }#endif - haswell_broadwell_cpu =0 ; +return false; +} + +/* +* Check if the CPU is Intel Haswell or Broadwell, +* because PCI relaxed ordering has no performance benefit with these CPUs.
+ */drivers/common/mlx5/mlx5_common.c +9
-0+bool mlx5_cpu_is_haswell_broadwell (void ) +{ +static bool haswell_broadwell_cpu; +static bool once = false; + +if (once) +return haswell_broadwell_cpu; + once = true; +return haswell_broadwell_cpu =mlx5_x86_is_haswell_broadwell (); }/** drivers/common/mlx5/mlx5_common.h +3
-0@@ -243,6 +243,9 @@ struct mlx5_klm {LIST_HEAD (mlx5_dbr_page_list, mlx5_devx_dbr_page); +__rte_internal +bool mlx5_cpu_is_haswell_broadwell(void); +__rte_internal enum mlx5_class mlx5_class_get(struct rte_devargs *devargs);
__rte_internal@@ -255,6 +258,5 @@int64_tmlx5_get_dbr(void *ctx, structmlx5_dbr_page_list*head,__rte_internalint32_tmlx5_release_dbr(structmlx5_dbr_page_list*head,uint32_tumem_id,drivers/common/mlx5/mlx5_common.h +0
-1uint64_t offset); -extern uint8_t haswell_broadwell_cpu;#endif /* RTE_PMD_MLX5_COMMON_H_ */ drivers/common/mlx5/rte_common_mlx5_version.map +2
-0@@ -6,6 +6,8 @@ INTERNAL { mlx5_common_verbs_reg_mr; mlx5_common_verbs_dereg_mr; + mlx5_cpu_is_haswell_broadwell; + mlx5_create_mr_ext; mlx5_dev_to_pci_addr;(quoted diff) +0
-0
b/drivers/net/mlx5/mlx5_flow_dv.cindex8b5b6838fa..f1109ae095100644drivers/net/mlx5/mlx5_flow_dv.c +1
-1@@ -4201,7 +4201,7 @@ flow_dv_create_counter_stat_mem_mng(struct rte_eth_dev *dev, int raws_n) mkey_attr.klm_num = 0;if (priv->config.hca_attr.relaxed_ordering_write && priv->config.hca_attr.relaxed_ordering_read && - !haswell_broadwell_cpu) + !mlx5_cpu_is_haswell_broadwell ()) mkey_attr.relaxed_ordering =1 ; mem_mng->dm = mlx5_devx_cmd_mkey_create(sh->ctx,
&mkey_attr);
if (!mem_mng->dm) {
--
2.27.0
19/07/2020 12:56, Matan Azrad:
Quoted 9 lines
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
I depends on linker options.
Quoted 4 lines
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example -rte_eth_devices.
There is more control and more abstraction in functions, it can provide futre-proof abstraction.
We should not export variables at all,
it is a basic rule of writing API.
Having a bad example in ethdev doesn't mean we should follow it.
Quoted 4 lines
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once and doesn't depend in any parameter.
Constructor must remain minimal.
If constructor can be avoided, it must be.
This is a golden rule.
Quoted 1 line
Quoted 1 line
Note: the priority of the constructor was probably irrelevant.
No comment about the constructor priority which was set as LOG for no good reason, proving that this code was not well reviewed?
Quoted 8 lines
Quoted 8 lines
At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering in unsuitableCPUs")
Cc: [email protected]
Cc: [email protected]Signed-off-by Thomas Monjalon <[email protected]>
From: Thomas Monjalon:
Quoted 13 lines
19/07/2020 12:56, Matan Azrad:
Quoted 9 lines
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
I depends on linker options.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example -rte_eth_devices.There is more control and more abstraction in functions, it can provide futre- proof abstraction.
Also variable have more abstraction - struct. In future, if it will be needed, we can change it.
Quoted 2 lines
We should not export variables at all,
it is a basic rule of writing API.
It is variable which is depended only in the running CPU - almost like compile time condition, so it is not regular case.
I think it makes sense also to use a singleton variable as internal API.
Quoted 1 line
Having a bad example in ethdev doesn't mean we should follow it.
If ethdev rte_eth_devices is bad API, Are you going to change it?
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once
and doesn't depend in any parameter.
Constructor must remain minimal.
If constructor can be avoided, it must be.
This is a golden rule.
The cpu detection is a fast code.
Using constructor here makes sense:
1. we need only one initialization for all the program.
2. no need to take care of multithreading on the single initialization (are your code thread safe?).
3. no parameters are required.
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
Note: the priority of the constructor was probably irrelevant.
No comment about the constructor priority which was set as LOG for no good reason, proving that this code was not well reviewed?
I guess you mean that comment is missing - you right.
We want to be sure that the variable is ready before any usage of it in the drivers (even in driver contractors).
Quoted 12 lines
Quoted 10 lines
Quoted 10 lines
At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering inunsuitable
CPUs")
Cc: [email protected]
Cc: [email protected]Signed-off-by Thomas Monjalon <[email protected]>
19/07/2020 13:41, Matan Azrad:
Quoted 29 lines
From: Thomas Monjalon:
Quoted 13 lines
19/07/2020 12:56, Matan Azrad:
Quoted 9 lines
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
I depends on linker options.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example -rte_eth_devices.There is more control and more abstraction in functions, it can provide futre- proof abstraction.
Also variable have more abstraction - struct. In future, if it will be needed, we can change it.
Quoted 2 lines
We should not export variables at all,
it is a basic rule of writing API.
Quoted 7 lines
It is variable which is depended only in the running CPU - almost like compile time condition, so it is not regular case.
I think it makes sense also to use a singleton variable as internal API.Quoted 1 line
Having a bad example in ethdev doesn't mean we should follow it.
If ethdev
rte_eth_devicesis bad API, Are you going to change it?
No, we avoid changing API.
Quoted 10 lines
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once
and doesn't depend in any parameter.
Constructor must remain minimal.
If constructor can be avoided, it must be.
This is a golden rule.
Quoted 5 lines
The cpu detection is a fast code.
Using constructor here makes sense:
1. we need only one initialization for all the program.
2. no need to take care of multithreading on the single initialization (are your code thread safe?).
I don't see what could be the issue.
Quoted 8 lines
3. no parameters are required.
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Note: the priority of the constructor was probably irrelevant.
No comment about the constructor priority which was set as LOG for no good reason, proving that this code was not well reviewed?
I guess you mean that comment is missing - you right.
No I mean this constructor is declared with LOG priority, but it is not doing any log registration.
Quoted 1 line
We want to be sure that the variable is ready before any usage of it in the drivers (even in driver contractors).
It is not used by other constructors.
And avoiding constructor dependencies is exactly why we avoid using constructors at all.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering inunsuitable
CPUs")
Cc: [email protected]
Cc: [email protected]Signed-off-by Thomas Monjalon <[email protected]>
Hi Thomas
From: Thomas Monjalon:
Quoted 15 lines
19/07/2020 13:41, Matan Azrad:
Quoted 14 lines
From: Thomas Monjalon:
Quoted 12 lines
19/07/2020 12:56, Matan Azrad:
Quoted 9 lines
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
I depends on linker options.
It will be good to add here the compiling command which failed for you...
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example -rte_eth_devices.There is more control and more abstraction in functions, it can provide futre- proof abstraction.
Also variable have more abstraction - struct. In future, if it will be needed, we can change it.
Quoted 2 lines
We should not export variables at all, it is a basic rule of writing API.
It is variable which is depended only in the running CPU - almost like compile time condition, so it is not regular case.
I think it makes sense also to use a singleton variable as internal API.
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Having a bad example in ethdev doesn't mean we should follow it.
If ethdev
rte_eth_devicesis bad API, Are you going to change it?No, we avoid changing API.
It is internal API, I don't understand your concern...
Quoted 11 lines
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once
and doesn't depend in any parameter.
Constructor must remain minimal.
If constructor can be avoided, it must be.
This is a golden rule.
Quoted 8 lines
Quoted 5 lines
The cpu detection is a fast code.
Using constructor here makes sense:
1. we need only one initialization for all the program.
2. no need to take care of multithreading on the single initialization (areyour code thread safe?).
I don't see what could be the issue.
2 mlx5 devices running configuration from 2 different threads. The first MR from each one of the devices can be created at the same time. The ask for the relaxed ordering cpu can be happened at the same time.
Quoted 4 lines
Quoted 4 lines
3. no parameters are required.
Quoted 2 lines
Quoted 1 line
Quoted 1 line
Note: the priority of the constructor was probably irrelevant.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
No comment about the constructor priority which was set as LOG for no good reason, proving that this code was not well reviewed?
I guess you mean that comment is missing - you right.
No I mean this constructor is declared with LOG priority, but it is not doing any log registration.
I hope you understand the motivation for higher priority, The LOG is just the one above.
Quoted 6 lines
Quoted 1 line
We want to be sure that the variable is ready before any usage of it in the
drivers (even in driver contractors).
It is not used by other constructors.
And avoiding constructor dependencies is exactly why we avoid using constructors at all.
Yes, It is for future, because it makes sense the cpu detection query will be done at initialization time.
Now, when I understand the community relevant guys don't like priorities(also I didn't convinced on the reasons), I think you can call it from common init function because it is the first call of mlx5 constructors.
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering inunsuitable
CPUs")
Cc: [email protected]
Cc: [email protected]Signed-off-by Thomas Monjalon <[email protected]>
We need to fix the race issue introduced by this patch.
My favor is to call it from constructor.
In any case we should validate the patch on ARM and Intel cores... The relaxes ordering original patch had a lot of testing before applying, Need to be sure we don't break nothing.
Matan
24/07/2020 17:43, Matan Azrad:
Quoted 64 lines
Hi Thomas
From: Thomas Monjalon:
Quoted 15 lines
19/07/2020 13:41, Matan Azrad:
Quoted 14 lines
From: Thomas Monjalon:
Quoted 12 lines
19/07/2020 12:56, Matan Azrad:
Quoted 9 lines
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
I depends on linker options.
It will be good to add here the compiling command which failed for you...
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example -rte_eth_devices.There is more control and more abstraction in functions, it can provide futre- proof abstraction.
Also variable have more abstraction - struct. In future, if it will be needed, we can change it.
Quoted 2 lines
We should not export variables at all, it is a basic rule of writing API.
It is variable which is depended only in the running CPU - almost like compile time condition, so it is not regular case.
I think it makes sense also to use a singleton variable as internal API.Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Having a bad example in ethdev doesn't mean we should follow it.
If ethdev
rte_eth_devicesis bad API, Are you going to change it?No, we avoid changing API.
It is internal API, I don't understand your concern...
Quoted 16 lines
Quoted 16 lines
Quoted 10 lines
Quoted 5 lines
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once
and doesn't depend in any parameter.
Constructor must remain minimal.
If constructor can be avoided, it must be.
This is a golden rule.The cpu detection is a fast code.
Using constructor here makes sense:
1. we need only one initialization for all the program.
2. no need to take care of multithreading on the single initialization (are
Quoted 7 lines
Quoted 3 lines
your code thread safe?).
I don't see what could be the issue.
2 mlx5 devices running configuration from 2 different threads. The first MR from each one of the devices can be created at the same time. The ask for the relaxed ordering cpu can be happened at the same time.
DPDK configuration is not thread safe.
Do you know any DPDK application configuring devices in 2 different threads?
Quoted 18 lines
Quoted 4 lines
Quoted 4 lines
3. no parameters are required.
Quoted 2 lines
Quoted 1 line
Quoted 1 line
Note: the priority of the constructor was probably irrelevant.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
No comment about the constructor priority which was set as LOG for no good reason, proving that this code was not well reviewed?
I guess you mean that comment is missing - you right.
No I mean this constructor is declared with LOG priority, but it is not doing any log registration.
I hope you understand the motivation for higher priority, The LOG is just the one above.
Quoted 3 lines
Quoted 1 line
We want to be sure that the variable is ready before any usage of it in the
drivers (even in driver contractors).
Quoted 7 lines
Quoted 3 lines
It is not used by other constructors.
And avoiding constructor dependencies is exactly why we avoid using constructors at all.Yes, It is for future, because it makes sense the cpu detection query will be done at initialization time.
Now, when I understand the community relevant guys don't like priorities(also I didn't convinced on the reasons), I think you can call it from common init function because it is the first call of mlx5 constructors.
We want to avoid priorities, and more importantly, we want to avoid having too much code in constructors.
Quoted 2 lines
We need to fix the race issue introduced by this patch.
My favor is to call it from constructor.
Initialization and configuration is supposed to be done by a single thread. There should not have any race condition.
Hi Thomas
From: Thomas Monjalon:
Quoted 21 lines
24/07/2020 17:43, Matan Azrad:
Quoted 20 lines
Hi Thomas
From: Thomas Monjalon:
Quoted 15 lines
19/07/2020 13:41, Matan Azrad:
Quoted 14 lines
From: Thomas Monjalon:
Quoted 12 lines
19/07/2020 12:56, Matan Azrad:
Quoted 9 lines
From: Thomas Monjalon
Quoted 5 lines
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD because it was not exported as part of the .map file.
Can you explain exactly when it is not visible?
I depends on linker options.
It will be good to add here the compiling command which failed for you...
?
Quoted 46 lines
Quoted 46 lines
Quoted 18 lines
Quoted 18 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It is fixed by exporting a function, which is cleaner than a variable.
Can you explain why?
We have classic example -rte_eth_devices.There is more control and more abstraction in functions, it can provide futre- proof abstraction.
Also variable have more abstraction - struct. In future, if it will be needed, we can change it.
Quoted 2 lines
We should not export variables at all, it is a basic rule of writing API.
It is variable which is depended only in the running CPU - almost like compile time condition, so it is not regular case.
I think it makes sense also to use a singleton variable as internal API.Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Having a bad example in ethdev doesn't mean we should follow it.
If ethdev
rte_eth_devicesis bad API, Are you going to change it?No, we avoid changing API.
It is internal API, I don't understand your concern...
Quoted 19 lines
Quoted 11 lines
Quoted 10 lines
Quoted 5 lines
Quoted 2 lines
By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Yes, but why not to do it in constructor? this variable is initialized only once
and doesn't depend in any parameter.
Constructor must remain minimal.
If constructor can be avoided, it must be.
This is a golden rule.Quoted 6 lines
The cpu detection is a fast code.
Using constructor here makes sense:
1. we need only one initialization for all the program.
2. no need to take care of multithreading on the single initialization (areyour code thread safe?).
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
I don't see what could be the issue.
2 mlx5 devices running configuration from 2 different threads. The first MR from each one of the devices can be created at the same time. The ask for the relaxed ordering cpu can be happened at the same time.
DPDK configuration is not thread safe.
Do you know any DPDK application configuring devices in 2 different threads?
A lot of effort were done in our driver and in other areas in dpdk in order to protect this scenario, we need to follow.
One case is failsafe, configuration can be done from either host thread or the caller thread.
Also, we may configure MR from data-path cores.
Quoted 24 lines
Quoted 17 lines
Quoted 4 lines
Quoted 4 lines
3. no parameters are required.
Quoted 2 lines
Quoted 1 line
Quoted 1 line
Note: the priority of the constructor was probably irrelevant.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
No comment about the constructor priority which was set as LOG for no good reason, proving that this code was not well reviewed?
I guess you mean that comment is missing - you right.
No I mean this constructor is declared with LOG priority, but it is not doing any log registration.
I hope you understand the motivation for higher priority, The LOG is just the one above.
Quoted 2 lines
Quoted 2 lines
We want to be sure that the variable is ready before any usage of it in the
Quoted 7 lines
Quoted 5 lines
drivers (even in driver contractors).
It is not used by other constructors.
And avoiding constructor dependencies is exactly why we avoid using constructors at all.Yes, It is for future, because it makes sense the cpu detection query will be
Quoted 8 lines
done at initialization time.
Quoted 2 lines
Now, when I understand the community relevant guys don't like
priorities(also I didn't convinced on the reasons), I think you can call it from common init function because it is the first call of mlx5 constructors.
We want to avoid priorities, and more importantly, we want to avoid having too much code in constructors.
The code here is not too much and as I said it makes sense to do this prior code in constructor.
Quoted 5 lines
Quoted 2 lines
We need to fix the race issue introduced by this patch.
My favor is to call it from constructor.Initialization and configuration is supposed to be done by a single thread. There should not have any race condition.
So, please explain all the dpdk effort to protect it....
Quoted 61 lines · Thomas Monjalon
The detection of the CPU was done in a constructor and shared in a global variable.
This variable may not be visible in the net PMD
because it was not exported as part of the .map file.
It is fixed by exporting a function, which is cleaner than a variable.By checking the CPU only at the first call of the function, doing the check in a constructor becomes useless.
Note: the priority of the constructor was probably irrelevant.At the same time, the comments are reworded or dropped if useless.
Fixes 4c204fe5e5d2 ("common/mlx5: disable relaxed ordering in unsuitable CPUs")Signed-off-by Thomas Monjalon <[email protected]>--- drivers/common/mlx5/linux/mlx5_common_verbs.c | 2 +- drivers/common/mlx5/mlx5_common.c | 53 ++++++++----------- drivers/common/mlx5/mlx5_common.h | 4 +- .../common/mlx5/rte_common_mlx5_version.map | 2 + drivers/net/mlx5/mlx5_flow_dv.c | 2 +- 5 files changed, 28 insertions(+), 35 deletions(-)drivers/common/mlx5/linux/mlx5_common_verbs.c +1
-1@@ -55,7 +55,7 @@ mlx5_common_verbs_reg_mr(void *pd, void *addr, size_t length,memset (pmd_mr,0 ,sizeof (*pmd_mr)); ibv_mr = mlx5_glue->reg_mr (pd, addr, length,IBV_ACCESS_LOCAL_WRITE | - (haswell_broadwell_cpu ?0 : + (mlx5_cpu_is_haswell_broadwell () ?0 :IBV_ACCESS_RELAXED_ORDERING ));if (!ibv_mr)return -1 ;drivers/common/mlx5/mlx5_common.c +0
-5@@ -20,8 +20,6 @@ int mlx5_common_logtype;const struct mlx5_glue *mlx5_glue;#endif -uint8_t haswell_broadwell_cpu; -static int mlx5_class_check_handler(__rte_unused const char *key, const char *value,void *opaque)@@ -59,19 +57,8 @@ mlx5_class_get(struct rte_devargs *devargs) } -/* In case this is an x86_64 intel processor to check if -* we should use relaxed ordering. -*/ #ifdef RTE_ARCH_X86_64
drivers/common/mlx5/mlx5_common.c mlx5_class_get(struct rte_devargs *devargs) · line 61
Quoted 10 lines
drivers/common/mlx5/mlx5_common.c +1
-9-/** -* This function returns processor identification and feature information -* into the registers. -* -* @param eax, ebx, ecx, edx -* Pointers to the registers that will hold cpu information. -* @param level -* The main category of information returned. -*/ +/* Processor identification and feature information filled in registers. */
Nit, no need for inline.
Quoted 117 lines
drivers/common/mlx5/mlx5_common.c +20
-18static inline void mlx5_cpu_id (unsigned int level,unsigned int *eax,unsigned int *ebx,unsigned int *ecx,unsigned int *edx)@@ -97,17 +84,7 @@ RTE_INIT_PRIO(mlx5_glue_init, CLASS)mlx5_glue_constructor (); } -/** -* This function is responsible of initializing the variable -* haswell_broadwell_cpu by checking if the cpu is intel -* and reading the data returned from mlx5_cpu_id(). -* since haswell and broadwell cpus don't have improved performance -* when using relaxed ordering we want to check the cpu type before -* before deciding whether to enable RO or not. -* if the cpu is haswell or broadwell the variable will be set to 1 -* otherwise it will be 0. -*/ -RTE_INIT_PRIO(mlx5_is_haswell_broadwell_cpu, LOG) +static bool mlx5_x86_is_haswell_broadwell (void ) {#ifdef RTE_ARCH_X86_64 unsigned int broadwell_models[4 ] = {0x3d ,0x47 ,0x4F ,0x56 };@@ -125,8 +102,7 @@ RTE_INIT_PRIO(mlx5_is_haswell_broadwell_cpu, LOG) vendor = ebx; max_level = eax;if (max_level <1 ) { - haswell_broadwell_cpu =0 ; -return ; +return false; }mlx5_cpu_id (1 , &eax, &ebx, &ecx, &edx); model = (eax >>4 ) &0x0f ;@@ -140,18 +116,31 @@ RTE_INIT_PRIO(mlx5_is_haswell_broadwell_cpu, LOG)if (brand_id ==0 && family ==0x6 ) {for (i =0 ; i <RTE_DIM (broadwell_models); i++)if (model == broadwell_models[i]) { - haswell_broadwell_cpu =1 ; -return ; +return true; }for (i =0 ; i <RTE_DIM (haswell_models); i++)if (model == haswell_models[i]) { - haswell_broadwell_cpu =1 ; -return ; +return true; } } }#endif - haswell_broadwell_cpu =0 ; +return false; +} + +/* +* Check if the CPU is Intel Haswell or Broadwell, +* because PCI relaxed ordering has no performance benefit with these CPUs. +*/ +bool mlx5_cpu_is_haswell_broadwell (void ) +{ +static bool haswell_broadwell_cpu; +static bool once = false; + +if (once) +return haswell_broadwell_cpu; + once = true; +return haswell_broadwell_cpu =mlx5_x86_is_haswell_broadwell (); }/** drivers/common/mlx5/mlx5_common.h +3
-1@@ -243,6 +243,9 @@ struct mlx5_klm {LIST_HEAD (mlx5_dbr_page_list, mlx5_devx_dbr_page); +__rte_internal +bool mlx5_cpu_is_haswell_broadwell(void); +__rte_internal enum mlx5_class mlx5_class_get(struct rte_devargs *devargs); __rte_internal@@ -255,6 +258,5 @@ int64_t mlx5_get_dbr(void *ctx, struct mlx5_dbr_page_list *head,__rte_internal int32_t mlx5_release_dbr(struct mlx5_dbr_page_list *head, uint32_t umem_id,uint64_t offset); -extern uint8_t haswell_broadwell_cpu;#endif /* RTE_PMD_MLX5_COMMON_H_ */ drivers/common/mlx5/rte_common_mlx5_version.map +2
-0@@ -6,6 +6,8 @@ INTERNAL { mlx5_common_verbs_reg_mr; mlx5_common_verbs_dereg_mr; + mlx5_cpu_is_haswell_broadwell; + mlx5_create_mr_ext; mlx5_dev_to_pci_addr;drivers/net/mlx5/mlx5_flow_dv.c +1
-2@@ -4201,7 +4201,7 @@ flow_dv_create_counter_stat_mem_mng(struct rte_eth_dev *dev, int raws_n) mkey_attr.klm_num =0 ;if (priv->config.hca_attr.relaxed_ordering_write && priv->config.hca_attr.relaxed_ordering_read && - !haswell_broadwell_cpu) + !mlx5_cpu_is_haswell_broadwell ()) mkey_attr.relaxed_ordering =1 ; mem_mng->dm =mlx5_devx_cmd_mkey_create (sh->ctx, &mkey_attr);if (!mem_mng->dm) { --
Quoted 2 lines
2.27.0
I ended up on this constructor hack while looking at the common code. This patch makes sense.
Signature · 1 line
David Marchand