05/05/2021 05:43, Chengwen Feng:
Currently, the mp uses gettimeofday() API to get the time, and used as timeout parameter.
But the time which gets from gettimeofday() API isn't monotonically increasing. The process may fail if the system time is changed.
This fixes it by using clock_gettime() API with monotonic attribution.
Fixes: 783b6e54971d ("eal: add synchronous multi-process communication") Fixes: f05e26051c15 ("eal: add IPC asynchronous request") Cc: stable@dpdk.org
Signed-off-by: Chengwen Feng fengchengwen@huawei.com Signed-off-by: Min Hu (Connor) humin29@huawei.com Acked-by: Morten Brørup mb@smartsharesystems.com
v3:
- add acked-by.
- change patch's author.
I did some comments on v2 about potential errors to catch, but you sent this v3 without participating in v2 discussion.
On 2021/5/11 15:36, Thomas Monjalon wrote:
05/05/2021 05:43, Chengwen Feng:
Currently, the mp uses gettimeofday() API to get the time, and used as timeout parameter.
But the time which gets from gettimeofday() API isn't monotonically increasing. The process may fail if the system time is changed.
This fixes it by using clock_gettime() API with monotonic attribution.
Fixes: 783b6e54971d ("eal: add synchronous multi-process communication") Fixes: f05e26051c15 ("eal: add IPC asynchronous request") Cc: stable@dpdk.org
Signed-off-by: Chengwen Feng fengchengwen@huawei.com Signed-off-by: Min Hu (Connor) humin29@huawei.com Acked-by: Morten Brørup mb@smartsharesystems.com
v3:
- add acked-by.
- change patch's author.
I did some comments on v2 about potential errors to catch, but you sent this v3 without participating in v2 discussion.
Fixed in v4, thanks
.
-
fengchengwen -
Thomas Monjalon