From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Naga Harish K S V <s.v.naga.harish.k@intel.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: [RFC 2/6] eventdev: avoid use of pthread_cancel
Date: Wed, 24 Sep 2025 09:51:09 -0700 [thread overview]
Message-ID: <20250924165527.268645-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20250924165527.268645-1-stephen@networkplumber.org>
To control the rx event thread is simpler and safer to
just close the file descriptor rather than using pthread_cancel().
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/eventdev/rte_event_eth_rx_adapter.c | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/lib/eventdev/rte_event_eth_rx_adapter.c b/lib/eventdev/rte_event_eth_rx_adapter.c
index 994f256322..95ceb35c5a 100644
--- a/lib/eventdev/rte_event_eth_rx_adapter.c
+++ b/lib/eventdev/rte_event_eth_rx_adapter.c
@@ -1173,9 +1173,11 @@ rxa_intr_thread(void *arg)
while (1) {
n = rte_epoll_wait(rx_adapter->epd, epoll_events,
RTE_EVENT_ETH_INTR_RING_SIZE, -1);
- if (unlikely(n < 0))
- RTE_EDEV_LOG_ERR("rte_epoll_wait returned error %d",
- n);
+ if (unlikely(n < 0)) {
+ RTE_EDEV_LOG_ERR("rte_epoll_wait returned error %d", n);
+ break;
+ }
+
for (i = 0; i < n; i++) {
rxa_intr_ring_enqueue(rx_adapter,
epoll_events[i].epdata.data);
@@ -1643,10 +1645,12 @@ rxa_destroy_intr_thread(struct event_eth_rx_adapter *rx_adapter)
{
int err;
- err = pthread_cancel((pthread_t)rx_adapter->rx_intr_thread.opaque_id);
- if (err)
- RTE_EDEV_LOG_ERR("Can't cancel interrupt thread err = %d",
- err);
+ /*
+ * close the epoll fd used in the interrupt thread
+ * this will unblock the rte_epoll_wait().
+ */
+ close(rx_adapter->epd);
+ rx_adapter->epd = INIT_FD;
err = rte_thread_join(rx_adapter->rx_intr_thread, NULL);
if (err)
@@ -1671,9 +1675,6 @@ rxa_free_intr_resources(struct event_eth_rx_adapter *rx_adapter)
if (ret)
return ret;
- close(rx_adapter->epd);
- rx_adapter->epd = INIT_FD;
-
return ret;
}
--
2.47.3
next prev parent reply other threads:[~2025-09-24 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 16:51 [RFC 0/6] get rid " Stephen Hemminger
2025-09-24 16:51 ` [RFC 1/6] eal: avoid using pthread_cancel Stephen Hemminger
2025-09-24 16:51 ` Stephen Hemminger [this message]
2025-09-24 16:51 ` [RFC 3/6] raw/ifpga: avoid use of pthread_cancel Stephen Hemminger
2025-09-24 16:51 ` [RFC 4/6] dma/skeleton: " Stephen Hemminger
2025-09-25 1:20 ` fengchengwen
2025-09-24 16:51 ` [RFC 5/6] intel/ipn3ke: " Stephen Hemminger
2025-09-24 16:51 ` [RFC 6/6] intel/iavf: remove " Stephen Hemminger
2025-09-25 15:11 ` Bruce Richardson
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=20250924165527.268645-3-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=s.v.naga.harish.k@intel.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).