From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id BFCA13B29E for ; Sat, 7 Nov 2020 12:26:15 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1604769972; bh=36GxWOJXtfx5Uzy3sX2sa94WiVi5Ps5d0y7H/ltjb7o=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=Jb/6vIUTzh7XAtKTVkzBUOTHRLzdk3Xyq0EsIcJVWovNSSnv6u3C0mU9uBzLh4Hbk W77f8jySkMRrxBfplcaNl4WC1NmMsRDfp7l66p4lLcr+1W86XgRyoAmcze4czqBTQD PbVPHy8O6heqn9WB9nnkk5wC3bWrWiVjiPPKWIiU= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.42.222] ([77.0.223.2]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N4zAy-1k9mfg2jTw-010uMH; Sat, 07 Nov 2020 18:26:12 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) From: Sebastian Moeller In-Reply-To: Date: Sat, 7 Nov 2020 18:26:11 +0100 Cc: Jesper Dangaard Brouer , Bloat Content-Transfer-Encoding: quoted-printable Message-Id: <290D7981-A5B9-41A0-A075-1E29366A87FA@gmx.de> References: <87imalumps.fsf@toke.dk> <871rh8vf1p.fsf@toke.dk> <81ED2A33-D366-42FC-9344-985FEE8F11BA@creamfinance.com> <87sg9ot5f1.fsf@toke.dk> <20201105143317.78276bbc@carbon> <11812D44-BD46-4CA4-BA39-6080BD88F163@creamfinance.com> <20201106121840.7959ae4b@carbon> <87blgaso84.fsf@toke.dk> <20201106135358.09f6c281@carbon> <20201106151324.5f506574@carbon> <1E70B6D2-1212-43FA-989A-03B657EEE2F2@creamfinance.com> <20201106211940.4c30ccc9@carbon> <20201107174623.73f91841@carbon> To: Thomas Rosenstein X-Mailer: Apple Mail (2.3445.104.17) X-Provags-ID: V03:K1:cwtuRBF1nO84rsBDVcWaN9Rm4BsWEuTDGpHLroIt71fyY4Zsagc 9HWWUF8OyZtykoriEFXnGaEcVHWVC69x4X4ouGGqPcfTrIv6P5O7NdgeooRZqkYrFCZcm/5 lNS+GP/xOuzWeh9j478N8u236oCJjo5/FaOB20q8+NtXCw9npXdlDLV5zyvl1oE4gRyQKqx aeSsBBUbimgvWXPkK/DWQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:rCJJcb+eEsk=:At2rf2RXI6J/neSWXIGPIC qOixMUQn8XPzvC1Kb5ET67wXVjOHFTYvYL/mRjuWPgqmfbONGooR02IAfWTZNwChpTVfhkMC3 kDPKdw8iqNQ78kshvmzzLEyO/ZA2lK1xCTK8luqVyAN5/NDEBF1NY+bJjIqw/aBiKItl//6Uh 9iE7YduMSaRk01OMSxjOXZF/wO72P6kujlZa/22hjfJa7n8fHlJ6LAEaPXpjlhYTaEp+TzB1S fqubh4vU3banNwQrhBKgJ/tjaVDqImCeGLyaAnF6ANhsM+WAnzRDmpXedagiDVCT2KFT/oFQA shhIF9b2m1RpC39XOWgo3buCkc5QriE6w5byY4Kg/hzKNNRsWzWjMEEhzdOmg8/11WxgBZPCQ DeTY3egccJoDbyu+BUw1Y26hg6uTFAe2amweY0RfoaYjGYAo1pY2QIBg7WfOZaCqxPPk1Sflk xqonzOCY/WLWFRTdOF0jieBkcL7V5aZdlmOjK4R75lNg9RorvOmbB3rugFI58MQqw9vXmyXmH 5hQjAe7bmyZm6LOorHu77Pp/jtg6GPYGXSjtgid4LOBHyqPrE0GJQbNHNGqeTxNXe25jc1zqo vRuo1UbZTBtYwzAQ8q/oY1g5QSajuTZKEAzxINiiqdtSf4XLIgwoo4YxDgtdOTIIalhUqCWeb y9qImmLtwbF16CJV9w2DuGTUNUuZLUsaGvAA0YkGnZrOkANpn4mTwYh5+K6pAOX7MDxOg54vc OL8/7GFg8jGD/8zosJtc2lDbh0ODOxVwEYjX11w1GP3lgupQkZE0tsjE6S+zI+zmp5g1JnX4t sd59hf0g28OZWK1EBOZC0Vl6q1zEoQrwVJttmi+8TJMpbg+1W98/fn6we6Y5VwvBiVtoStGBW /ue2K3YLHKoYfZTxrM6g== Subject: Re: [Bloat] Router congestion, slow ping/ack times with kernel 5.4.60 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2020 17:26:16 -0000 Hi Thomas, Probably not very helpful, but iputils' ping has the -D option that is = described as: -D Print timestamp (unix time + microseconds as in gettimeofday) = before each line. this potentially allows to be translated into kernel time to pinpoint = events in time? Not that I would know how to translate times here and if = perf and friends actually store timestamps.... Best Regards Sebastian > On Nov 7, 2020, at 18:01, Thomas Rosenstein via Bloat = wrote: >=20 >=20 >=20 > On 7 Nov 2020, at 17:46, Jesper Dangaard Brouer wrote: >=20 >>=20 >> Did the latency issue happen during this this perf recording? >> (it is obviously important that you record during the issue) >=20 > yes it was recorded during the transfer, while it exhibited the issue >=20 > I let the transfer run some time, then did the perf extract, stopped = the transfer afterwards. >=20 >>=20 >> Finding a single latency event/issue in perf.data is like looking in >> for needle in a haystack. It does give hints and e.g. tell me = details >> like what part of the kernel are used/activated. >>=20 >> I can see that you have likely configured XPS (Transmit Packet >> Steering). Is this on purpose? >=20 > Not on purpose, I assume it comes from the Mellanox Card. >=20 >>=20 >> --=20 >> Best regards, >> Jesper Dangaard Brouer >> MSc.CS, Principal Kernel Engineer at Red Hat >> LinkedIn: http://www.linkedin.com/in/brouer > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat