On Thu, Dec 14, 2023 at 10:28 AM Sevincer, Abdullah
wrote:
>
> Acked-by: Abdullah Sevincer
Updated the git commit as follows and applied to
dpdk-next-net-eventdev/for-main. Thanks
event/dlb2: remove unnecessary timer call
Consult the timer value only when the driver waits for a
tim
Bruce Richardson writes:
> On Wed, Dec 13, 2023 at 11:50:46AM -0500, Aaron Conole wrote:
>> Bruce Richardson writes:
>>
>> > We only need to consult the timer value when the driver waits for a
>> > timeout, so skip making the call to get the current timer/TSC value if
>> > the timeout is zero,
On Wed, Dec 13, 2023 at 11:50:46AM -0500, Aaron Conole wrote:
> Bruce Richardson writes:
>
> > We only need to consult the timer value when the driver waits for a
> > timeout, so skip making the call to get the current timer/TSC value if
> > the timeout is zero, as no wait will ever be done.
> >
Bruce Richardson writes:
> We only need to consult the timer value when the driver waits for a
> timeout, so skip making the call to get the current timer/TSC value if
> the timeout is zero, as no wait will ever be done.
>
> Signed-off-by: Bruce Richardson
> ---
Had a bad config value - retryin
Bruce Richardson writes:
> We only need to consult the timer value when the driver waits for a
> timeout, so skip making the call to get the current timer/TSC value if
> the timeout is zero, as no wait will ever be done.
>
> Signed-off-by: Bruce Richardson
> ---
Recheck-request: github-robot
Acked-by: Abdullah Sevincer
We only need to consult the timer value when the driver waits for a
timeout, so skip making the call to get the current timer/TSC value if
the timeout is zero, as no wait will ever be done.
Signed-off-by: Bruce Richardson
---
drivers/event/dlb2/dlb2.c | 6 --
1 file changed, 4 insertions(+),
7 matches
Mail list logo