Date: Wed, 08 Dec 2021 04:35:25 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Message-ID: <bug-221122-7501-EcpZSj9hbA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221122-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-221122-7501@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=3D221122 --- Comment #22 from Mason Loring Bliss <mason@blisses.org> --- Linux manages the trick on this same box, so the hardware can manage it=20 unless there's some critical difference I'm missing. I'd be happy to=20 explore from either side to shed more light on it. And sure, I can change=20 my model a bit and add a pool of epairs at boot and assign them=20 programmatically instead of using per-jail numbering and dynamic spin-up as I do today, but my interest in this started when I realized the delay was there in FreeBSD. Seems unfortunate for FreeBSD's handling to be less=20 capable than what Linux can do. That said, if I'm missing some concept that is different and matters, I'm eager to learn about it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221122-7501-EcpZSj9hbA>