Date: Sat, 29 May 2021 11:45:15 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 256217] [tcp] High system load because of interrupts with RACK Message-ID: <bug-256217-7501-trBIAVP4bN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256217-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-256217-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=3D256217 --- Comment #9 from Christos Chatzaras <chris@cretaforce.gr> --- HPTS system is "kern.eventtimer.timer=3DHPET", right? With HPET I see (with "top") ~ 2 times more interrupts in comparison with LAPIC. I tried again to reproduce the issue with a STABLE/13 kernel and it exists = too. Next I will try with a CURRENT kernel as I see some fixes for RACK. Regarding the "stuck" connection in LAST_ACK state someone tries to brute f= orce SSH and "sshguard" blocks the connections (I have 4 "stuck" connection for = SSH at the moment). Also I have 2 "stuck" connections in port 80 from "wrk benchmark". I found this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D25986 which is old PR b= ut @johalun replied that he can see this issue few months ago. But they are not talking about "rack" so this is not related. The only relation with "rack" = is that these "stuck" connections create interrupts. At the moment these connections "stuck" for more than 35 minutes. Also I see some "stuck" connections in other servers that use "freebsd" stack. --=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-256217-7501-trBIAVP4bN>