From: Yiding Zhou <yidingx.zhou@intel.com>
To: dev@dpdk.org
Cc: qi.z.zhang@intel.com, anatoly.burakov@intel.com,
xingguang.he@intel.com, Yiding Zhou <yidingx.zhou@intel.com>,
stable@dpdk.org
Subject: [PATCH v2] net/pcap: fix timeout of stopping device
Date: Tue, 6 Sep 2022 16:05:11 +0800 [thread overview]
Message-ID: <20220906080511.46088-1-yidingx.zhou@intel.com> (raw)
In-Reply-To: <20220825072041.10768-1-yidingx.zhou@intel.com>
The pcap file will be synchronized to the disk when stopping the device.
It takes a long time if the file is large that would cause the
'detach sync request' timeout when the device is closed under multi-process
scenario.
This commit fixes the issue by using alarm handler to release dumper.
Fixes: 0ecfb6c04d54 ("net/pcap: move handler to process private")
Cc: stable@dpdk.org
Signed-off-by: Yiding Zhou <yidingx.zhou@intel.com>
---
v2: use alarm handler to release dumper
---
drivers/net/pcap/pcap_ethdev.c | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/net/pcap/pcap_ethdev.c b/drivers/net/pcap/pcap_ethdev.c
index ec29fd6bc5..5c643a0277 100644
--- a/drivers/net/pcap/pcap_ethdev.c
+++ b/drivers/net/pcap/pcap_ethdev.c
@@ -17,6 +17,7 @@
#include <rte_mbuf_dyn.h>
#include <rte_bus_vdev.h>
#include <rte_os_shim.h>
+#include <rte_alarm.h>
#include "pcap_osdep.h"
@@ -664,6 +665,25 @@ eth_dev_start(struct rte_eth_dev *dev)
return 0;
}
+static void eth_pcap_dumper_release(void *arg)
+{
+ pcap_dump_close((pcap_dumper_t *)arg);
+}
+
+static void
+eth_pcap_dumper_close(pcap_dumper_t *dumper)
+{
+ if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
+ /*
+ * Delay 30 seconds before releasing dumper to wait for file sync
+ * to complete to avoid blocking alarm thread in PRIMARY process
+ */
+ rte_eal_alarm_set(30000000, eth_pcap_dumper_release, dumper);
+ } else {
+ rte_eal_alarm_set(1, eth_pcap_dumper_release, dumper);
+ }
+}
+
/*
* This function gets called when the current port gets stopped.
* Is the only place for us to close all the tx streams dumpers.
@@ -689,7 +709,7 @@ eth_dev_stop(struct rte_eth_dev *dev)
for (i = 0; i < dev->data->nb_tx_queues; i++) {
if (pp->tx_dumper[i] != NULL) {
- pcap_dump_close(pp->tx_dumper[i]);
+ eth_pcap_dumper_close(pp->tx_dumper[i]);
pp->tx_dumper[i] = NULL;
}
--
2.34.1
next prev parent reply other threads:[~2022-09-06 8:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 7:20 [PATCH] net/pcap: reduce time for stopping device Yiding Zhou
2022-08-25 10:09 ` Ferruh Yigit
2022-08-25 11:17 ` Zhou, YidingX
2022-08-25 12:21 ` Ferruh Yigit
2022-08-29 11:50 ` Zhou, YidingX
2022-08-31 16:42 ` Stephen Hemminger
2022-09-01 7:40 ` Zhou, YidingX
2022-09-06 8:05 ` Yiding Zhou [this message]
2022-09-06 14:57 ` [PATCH v2] net/pcap: fix timeout of " Stephen Hemminger
2022-09-06 16:21 ` Zhou, YidingX
2022-09-21 7:14 ` Zhou, YidingX
2022-10-03 15:00 ` Ferruh Yigit
2022-11-22 9:25 ` Zhou, YidingX
2022-11-22 17:28 ` Stephen Hemminger
2022-12-02 10:22 ` Zhou, YidingX
2022-11-29 14:11 ` Ferruh Yigit
2022-12-02 10:13 ` Zhou, YidingX
2022-12-02 11:19 ` Ferruh Yigit
2022-12-05 1:58 ` Zhou, YidingX
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=20220906080511.46088-1-yidingx.zhou@intel.com \
--to=yidingx.zhou@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=xingguang.he@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.