Date: Wed, 24 Mar 2021 15:16:01 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 254514] vnet: /sbin/ifconfig epair10b vnet $name getting stuck if one CPU is busy Message-ID: <bug-254514-27103-0fMoBvbEhb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254514-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-254514-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254514 andrew@tao11.riddles.org.uk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@tao11.riddles.org.uk --- Comment #1 from andrew@tao11.riddles.org.uk --- (In reply to Mina Gali=C4=87 from comment #0) > given that this is a side-effect of 1 CPU core being 100% busy, does this= mean that draining callbacks needs all CPUs? Yes, it does mean that. Draining epoch callbacks is done by having the thre= ad doing the drain bind itself to each cpu in turn, so it'll block if for any reason it can't be scheduled any runtime on some cpu (such as if a cpu is 1= 00% busy at a priority that doesn't let it be preempted by the drain). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254514-27103-0fMoBvbEhb>