From owner-freebsd-net@freebsd.org Tue Jan 30 14:40:28 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE7B2ECE1D3 for ; Tue, 30 Jan 2018 14:40:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30E716F631 for ; Tue, 30 Jan 2018 14:40:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8BB1A1DA6C for ; Tue, 30 Jan 2018 14:40:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0UEeRhM031972 for ; Tue, 30 Jan 2018 14:40:27 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0UEeRjT031970 for freebsd-net@FreeBSD.org; Tue, 30 Jan 2018 14:40:27 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 225535] Delays in TCP connection over Gigabit Ethernet connections; Regression from 6.3-RELEASE Date: Tue, 30 Jan 2018 14:40:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: aeder@list.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 14:40:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225535 --- Comment #13 from Aleksander Derevianko --- Results of tests with kern.eventtimer.periodic=3D0 seems very interesting: A1 computer: grep times periodic.txt | awk '{print $3 " " $4 " " $6 " " $8 " " $10;}' | = sort | uniq -c 18989 send_sync 0 0 0 0 1557 send_sync 0 0 0 1 3 send_sync 0 0 0 229 352 send_sync 0 1 0 0 A2 computer root@fspa2:~/clock/new_res # grep times periodic.txt | awk '{print $3 " " $= 4 " " $6 " " $8 " " $10 ;}' | sort | uniq -c 11498 send_sync 0 0 0 0 9621 send_sync 0 0 0 1 3 send_sync 0 0 0 2 4 send_sync 0 0 0 230 20 send_sync 0 1 0 0 root@fspa1:~/clock/new_res # grep times periodic.txt | grep recv_data\ 229 times 2554: send_sync 0 recv_sync 0 send_data 0 recv_data 229 eval 52 sleep= 19 times 7278: send_sync 0 recv_sync 0 send_data 0 recv_data 229 eval 52 sleep= 19 times 10424: send_sync 0 recv_sync 0 send_data 0 recv_data 229 eval 52 slee= p 19 root@fspa1:~/clock/new_res # times 18296: send_sync 0 recv_sync 0 send_data 0 recv_data 0 eval 52 sleep = 248 root@fspa2:~/clock/new_res # grep times periodic.txt| grep recv_data\ 230 times 2554: send_sync 0 recv_sync 0 send_data 0 recv_data 230 eval 52 sleep= 18 times 7278: send_sync 0 recv_sync 0 send_data 0 recv_data 230 eval 52 sleep= 18 times 10424: send_sync 0 recv_sync 0 send_data 0 recv_data 230 eval 52 slee= p 18 times 18296: send_sync 0 recv_sync 0 send_data 0 recv_data 230 eval 52 slee= p 18 root@fspa2:~/clock/new_res # As you can see, in 3 cases delay was catched on both sides, and in one case= - only in A2 computer. Moreover, it seems like A1 computer have 92% of all zeroes: 18989 send_sync 0 0 0 0 1557 send_sync 0 0 0 1 At the same time, A2 computer have only 54% of all zeroes: 11498 send_sync 0 0 0 0 9621 send_sync 0 0 0 1 I have found the difference in config: A1 root@fspa1:~/clock/new_res # cat /boot/loader.conf boot_verbose=3D"YES" coretemp_load=3D"YES" autoboot_delay=3D"-1" loader_logo=3D"fbsdbw" kern.ipc.semmns=3D350 hw.em.txd=3D"4096" hw.em.rxd=3D"4096" hw.em.rx_process_limit=3D"-1" hw.em.enable_msix=3D"0" A2 root@fspa2:~/clock/new_res # cat /boot/loader.conf console=3D"comconsole,vidconsole" coretemp_load=3D"YES" autoboot_delay=3D"-1" loader_logo=3D"fbsdbw" kern.ipc.semmns=3D"350" hw.em.txd=3D"4096" hw.em.rxd=3D"4096" hw.em.rx_process_limit=3D"-1" hw.em.enable_msix=3D"0" Can boot_verbose=3D"YES" or console=3D"comconsole,vidconsole" make such dif= ference? --=20 You are receiving this mail because: You are the assignee for the bug.=