> > > Because accuracy of timing to the microsecond is not guaranteed in
> > > rte_eal_alarm_set, this function will not be called before the
> > > requested time, but may be called a period of time afterwards which
> > > can not be calculated. In order to ensure test alarm running success,
> > > t
> >
> > -Original Message-
> > From: Yang, Qiming
> > Sent: Tuesday, June 20, 2017 11:24 AM
> > To: dev@dpdk.org
> > Cc: Chen, Jing D ; Wu, Jingjing
> > ; Yang, Qiming
> > Subject: [PATCH v3] test: add delay time in test alarm
> >
> > Because accuracy of timing to the microsecond is not g
Hi, Mark
"2" and "10" is the special number in this test case, not a general number.
/* Test that we cannot cancel an alarm from within the callback itself
* Also test that we can cancel head-of-line callbacks ok.*/
flag = 0;
recursive_error = 0;
rte_eal_ala
+ while (flag != 2 && count++ < RTE_TEST_MAX_REPEAT)
+ rte_delay_ms(10);
Why you don't replace "2" and "10" with macro?
-Original Message-
From: Yang, Qiming
Sent: Tuesday, June 20, 2017 11:24 AM
To: dev@dpdk.org
Cc: Chen, Jing D ; Wu, Jingjing ;
Yang, Qiming
Subje
Because accuracy of timing to the microsecond is not guaranteed
in rte_eal_alarm_set, this function will not be called before
the requested time, but may be called a period of time
afterwards which can not be calculated. In order to ensure
test alarm running success, this patch added the delay time
5 matches
Mail list logo
