On Wed, Sep 25, 2024 at 9:34 PM Wojciech Panfil
wrote:
>
> Issue:
> Two threads:
>
> - A, executing rte_eal_alarm_cancel,
> - B, executing eal_alarm_callback.
>
> Such case can cause starvation of thread B. Please see that there is a
> small time window between lock and unlock in thread A, so thre
On Wed, 25 Sep 2024 21:42:06 +0200
Wojciech Panfil wrote:
> Issue:
> Two threads:
>
> - A, executing rte_eal_alarm_cancel,
> - B, executing eal_alarm_callback.
>
> Such case can cause starvation of thread B. Please see that there is a
> small time window between lock and unlock in thread A, so
Issue:
Two threads:
- A, executing rte_eal_alarm_cancel,
- B, executing eal_alarm_callback.
Such case can cause starvation of thread B. Please see that there is a
small time window between lock and unlock in thread A, so thread B must
be switched to within a very small time window, so that it can
On Wed, 18 Sep 2024 13:39:06 +0200
Wojciech Panfil wrote:
> Issue:
> Two threads:
>
> - A, executing rte_eal_alarm_cancel,
> - B, executing eal_alarm_callback.
>
> Such case can cause starvation of thread B. Please see that there is a
> small time window between lock and unlock in thread A, so
Issue:
Two threads:
- A, executing rte_eal_alarm_cancel,
- B, executing eal_alarm_callback.
Such case can cause starvation of thread B. Please see that there is a
small time window between lock and unlock in thread A, so thread B must
be switched to within a very small time window, so that it can
Issue:
Two threads:
- A, executing rte_eal_alarm_cancel,
- B, executing eal_alarm_callback.
Such case can cause starvation of thread B. Please see that there is a
small time window between lock and unlock in thread A, so thread B must
be switched to within a very small time window, so that it can
6 matches
Mail list logo