summaryrefslogtreecommitdiffstats
path: root/sys
diff options
context:
space:
mode:
authorkensmith <kensmith@FreeBSD.org>2004-09-29 21:39:36 +0000
committerkensmith <kensmith@FreeBSD.org>2004-09-29 21:39:36 +0000
commita831027f1e9f217822054966e93d9ffb070fb33a (patch)
tree560861a911c2cca8c67e23d3ab5e39ccada30f89 /sys
parent611fe940a3f8e543d2d35ee4e4ac916e0c94f864 (diff)
downloadFreeBSD-src-a831027f1e9f217822054966e93d9ffb070fb33a.zip
FreeBSD-src-a831027f1e9f217822054966e93d9ffb070fb33a.tar.gz
We seem to have occasions where sending an IPI takes significantly
longer than 'normal'. The cause is still being tracked down but in the meantime there are machines where raising IPI_RETRIES does help - it's not just a case of the machine staying locked up longer and then panic-ing anyway. Several helpful folks on sparc64@ tried a patch that helped figure out what to raise this number to. Discussed on: sparc64@ MFC after: 3 days
Diffstat (limited to 'sys')
-rw-r--r--sys/sparc64/include/smp.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/sparc64/include/smp.h b/sys/sparc64/include/smp.h
index fba9eea..3f3b0b9 100644
--- a/sys/sparc64/include/smp.h
+++ b/sys/sparc64/include/smp.h
@@ -45,7 +45,7 @@
#define IPI_RENDEZVOUS PIL_RENDEZVOUS
#define IPI_STOP PIL_STOP
-#define IPI_RETRIES 100
+#define IPI_RETRIES 5000
struct cpu_start_args {
u_int csa_count;
OpenPOWER on IntegriCloud