From: Wojciech Panfil <wojciech.panfil@intel.com>
To: <bruce.richardson@intel.com>
Cc: <pallavi.kadam@intel.com>, <dev@dpdk.org>,
<jacek.kalwas@intel.com>, <konrad.sztyber@intel.com>,
<dmitry.kozliuk@gmail.com>, <roretzla@linux.microsoft.com>,
<wojciech.panfil@intel.com>
Subject: [PATCH] eal/alarm_cancel: Fix thread starvation
Date: Wed, 18 Sep 2024 09:02:12 +0200 [thread overview]
Message-ID: <20240918070212.10339-1-wojciech.panfil@intel.com> (raw)
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 obtain
the lock.
Solution to this problem is use sched_yield(), which puts current thread
(A) at the end of thread execution priority queue and allows thread B to
execute.
The issue can be observed e.g. on hot-pluggable device detach path.
On such path, rte_alarm can used to check if DPDK has completed
the detachment. Waiting for completion, rte_eal_alarm_cancel
is called, while another thread periodically calls eal_alarm_callback
causing the issue to occur.
Signed-off-by: Wojciech Panfil <wojciech.panfil@intel.com>
---
lib/eal/freebsd/eal_alarm.c | 5 +++++
lib/eal/linux/eal_alarm.c | 5 +++++
lib/eal/windows/eal_alarm.c | 4 ++++
3 files changed, 14 insertions(+)
diff --git a/lib/eal/freebsd/eal_alarm.c b/lib/eal/freebsd/eal_alarm.c
index 94cae5f4b6..8425b4f5a2 100644
--- a/lib/eal/freebsd/eal_alarm.c
+++ b/lib/eal/freebsd/eal_alarm.c
@@ -318,7 +318,12 @@ rte_eal_alarm_cancel(rte_eal_alarm_callback cb_fn, void *cb_arg)
}
ap_prev = ap;
}
+
rte_spinlock_unlock(&alarm_list_lk);
+
+ /* Yield control to a second thread executing eal_alarm_callback to avoid its starvation,
+ * as it is waiting for the lock we have just released. */
+ sched_yield();
} while (executing != 0);
if (count == 0 && err == 0)
diff --git a/lib/eal/linux/eal_alarm.c b/lib/eal/linux/eal_alarm.c
index eeb096213b..5326b1895f 100644
--- a/lib/eal/linux/eal_alarm.c
+++ b/lib/eal/linux/eal_alarm.c
@@ -248,7 +248,12 @@ rte_eal_alarm_cancel(rte_eal_alarm_callback cb_fn, void *cb_arg)
}
ap_prev = ap;
}
+
rte_spinlock_unlock(&alarm_list_lk);
+
+ /* Yield control to a second thread executing eal_alarm_callback to avoid its starvation,
+ * as it is waiting for the lock we have just released. */
+ sched_yield();
} while (executing != 0);
if (count == 0 && err == 0)
diff --git a/lib/eal/windows/eal_alarm.c b/lib/eal/windows/eal_alarm.c
index 052af4b21b..43e8d7881f 100644
--- a/lib/eal/windows/eal_alarm.c
+++ b/lib/eal/windows/eal_alarm.c
@@ -211,6 +211,10 @@ rte_eal_alarm_cancel(rte_eal_alarm_callback cb_fn, void *cb_arg)
}
rte_spinlock_unlock(&alarm_lock);
+
+ /* Yield control to a second thread executing eal_alarm_callback to avoid its starvation,
+ * as it is waiting for the lock we have just released. */
+ SwitchToThread();
} while (executing);
rte_eal_trace_alarm_cancel(cb_fn, cb_arg, removed);
--
2.46.0
next reply other threads:[~2024-09-18 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 7:02 Wojciech Panfil [this message]
2024-09-18 11:39 Wojciech Panfil
2024-09-18 16:06 ` Stephen Hemminger
2024-09-25 19:42 Wojciech Panfil
2024-09-28 16:40 ` Stephen Hemminger
2024-10-04 12:00 ` David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240918070212.10339-1-wojciech.panfil@intel.com \
--to=wojciech.panfil@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=jacek.kalwas@intel.com \
--cc=konrad.sztyber@intel.com \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).