Received: by 10.213.65.68 with SMTP id h4csp205028imn; Tue, 3 Apr 2018 18:55:00 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+blbnpePdf+57sH37ilARa+EFzHV8jXEKspMAlfu1Rh8cvlyhnChF9BTX/+IIwY7ZteJfS X-Received: by 2002:a17:902:830a:: with SMTP id bd10-v6mr16167339plb.322.1522806900334; Tue, 03 Apr 2018 18:55:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522806900; cv=none; d=google.com; s=arc-20160816; b=jhD7isriMT9a4I4Q9NIGmiqTzue6atpQBfcMv/2CfCb3ghN504YabKLBBPvxZkN+g3 cqDXddYRntsKt6XUCfgLw5uyonTtpZyU1FHZIoas15thNjooqLASitlTxKL+TLAEwyAC HvEMcsgOV9DB+NAB3d12/HrZ6spTGeTLYToGkvO/wXTHfjRONBEaAb7b98f8tAuJpgHu cnrkKMR4cg1Q8Vdp7sRDOTzoST4WKaQYUhR2NZAmNkZIKyevgWh60hTGNKhWgILQ7KY6 QCBel4PlbkL70xZluEhv/UDq/bt7E1CtwcsS3pyKhVynQALu+09IK9meU9T7rqS0kwx6 UMFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:mime-version:dkim-signature :arc-authentication-results; bh=x3c6NpnsBl6RpGlUDWEjl8H3Pscob0l+0lJRdmjOIrg=; b=eVgD7P+osGPcFEWQ0cmwUmdIw4VE32DwnNvGrIHDS8Rn9XCgrEuEaYaCkHEYXTkPeZ kIh0bIz+yvKiCkffbUrjmPxF0qDoF9hFBfLq9bd9M3h30Wic0Ie9yHOl5VRNgdWtqt6M s9D3GOjQi+5X6vMHoIsnkLQ+qUJ3LY+SBcH2JsbKq0G3l7yjE8NcNj3bPP6VsnECM3x1 SC3N4idg0KTt4shXaSoZZQM7hutmMdEvS3Ag29SzbibsQc8nBX0v0YMKAl61kOexNeSj thru5NrwTl0K7mYdYqngPEinAWEmzTNDfJsSDLsoZDm1RT8MT6jhOID1QNblXP6iG6yf epWw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=UP8U3lGf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 73-v6si4275250plf.286.2018.04.03.18.54.46; Tue, 03 Apr 2018 18:55:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=UP8U3lGf; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754957AbeDDBwW (ORCPT + 99 others); Tue, 3 Apr 2018 21:52:22 -0400 Received: from mail-ot0-f175.google.com ([74.125.82.175]:41642 "EHLO mail-ot0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753916AbeDDBwT (ORCPT ); Tue, 3 Apr 2018 21:52:19 -0400 Received: by mail-ot0-f175.google.com with SMTP id i28-v6so21628836otf.8; Tue, 03 Apr 2018 18:52:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=x3c6NpnsBl6RpGlUDWEjl8H3Pscob0l+0lJRdmjOIrg=; b=UP8U3lGfqwWUGjVH3iqFoplz45zkDqmAEKNcVoLYk9VmAVVlB6bUOIiSH+NWU9yKSY fDe6QHmlWAUdZGPu3XKcdaa3fc4Iv99siQioSbTnHCTJK8GM20zB2tD48tON/L/QeJhB ap92c3SdL8JN2ycnEpFZf59tbdLmJMzaFtqrGW9eDYJQDS2FTE8mLjEaXLIBVyqT91+i nmuNyK3oL6WGSK5mfnKVMUdh1xwaEVZNiTIRYdzid1DTmDMUAN2ojQ4qsXYxWtieVYHh P3kf6PvmE9vTu0+LNs+LRUZ38P/Dt6G6lYPnA/otQJ1xn2QR6Jt73aTG3MCpnVmh6UBS MJYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=x3c6NpnsBl6RpGlUDWEjl8H3Pscob0l+0lJRdmjOIrg=; b=t27t04UohHX2AIyLKMeYd+x1n8CO00dihgyLra2hci9SszN9OCqKTUTIfcMlezLS5i +3v1f/itmFCUetXGzdoBp/o9v62SXDHYqeR78ph6/2zVFx/IwfS+i4wOA5/PSwK2iTaV dc+qePGA7q8dvQO1lLqf27JlvkbwTqQSkee5/UIX+/c8HPUKDHwjpDzNmbYVF8mT2BjK yXYuskX1Jhs/zXVarKA/1B1nSFNzpPgU5a2MKRpGjcJPeCYPxZ3wr0bhtuQiUnV58kVa /voit3RuqCkl7SdrMHE4wd/97m+QwXKqXw8dvY4NWIasNq+faVPt4M94DqnKjvuI2rEo P1Xg== X-Gm-Message-State: ALQs6tDQ+ecFuS0o21XnUnytZ2d0W8Xyvb14U6mXwrYizHRO19r99XlK iXmnXsYICdtsdCGtub96/w/69fQRCNWD50DzPDA= X-Received: by 2002:a9d:61cf:: with SMTP id h15-v6mr10133739otk.312.1522806739148; Tue, 03 Apr 2018 18:52:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.57.66 with HTTP; Tue, 3 Apr 2018 18:51:38 -0700 (PDT) From: =?UTF-8?Q?Jo=C3=A3o_Paulo_Rechi_Vita?= Date: Tue, 3 Apr 2018 18:51:38 -0700 Message-ID: Subject: RTL8723BE performance regression To: Larry Finger , Yan-Hsuan Chuang , Ping-Ke Shih , Birming Chiu , Shaofu , Steven Ting , Chaoming Li , Kalle Valo Cc: linux-wireless , Network Development , LKML , Daniel Drake , =?UTF-8?Q?Jo=C3=A3o_Paulo_Rechi_Vita?= , linux@endlessm.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, I've been trying to track a performance regression on the RTL8723BE WiFi adapter, which mainly affects the upload bandwidth (although we can see a decreased download performance as well, the effect on upload is more drastic). This was first reported by users after upgrading from our 4.11-based kernel to our 4.13-based kernel, but also confirmed to affect our development branch (4.15-based kernel) and wireless-drivers-next at the wireless-drivers-next-for-davem-2018-03-29 tag. This is happening on an HP laptop that needs rtl8723be.ant_sel=3D1 (and all the following tests have been made with that param). My first bisect attempt pointed me to the following commit: bcd37f4a0831 rtlwifi: btcoex: 23b 2ant: let bt transmit when hw initialisation done Which I later found to be already fixed by a33fcba6ec01 rtlwifi: btcoexist: Fix breakage of ant_sel for rtl8723be. That fix is already included in v4.15 though (and our dev branch as well), so I did a second bisect, now cherry-picking a33fcba6ec01 at every step, and it pointed me to the following commit: 7937f02d1953 rtlwifi: btcoex: hook external functions for newer chips Reverting that commit on top of our development branch fixes the problem, but on top of v4.15 I get mixed results: a few times getting a good upload performance (~5-6Mbps) but most of the time just getting ~1-1.5Mpbs (which is still better than the 0.0 then test failure I've gotten on most bad points of the bisect). Bisecting the downstream patches we carry on top of v4.15 (we base our kernel on Ubuntu's, so there are quite a few downstream changes) did not bring any clarity, as at all bisect points (plus reverting 7937f02d1953) the performance was good, so probably there was some other difference in the resulting kernels from my initial revert of that patch on top of v4.15 and each step during the bisect. I've experimented a bit with fwlps=3D0, but it did not bring any conclusive results either. I'll try to look at other things that may have changed (configuration perhaps?), but I don't have a clear plan yet. Have you seen anything similar, or have any other ideas or suggestions to track this problem? Even without crystal clear results, it looks like 7937f02d1953 is having a negative impact on the RTL8723BE performance, so perhaps it is worth reverting it and reworking it a later point? This are the results (testing with speedtest.net) I got at some key points: Version Commit Ping Down Up v4.11 a351e9b 12 25.44 5.99 v4.11 a351e9b 131 17.02 5.89 v4.13 569dbb8 174 14.08 0.00 v4.13 569dbb8 261 8.41 0.00 v4.15+revert d8a5b80 19 23.86 1.41 v4.15+revert d8a5b80 189 18.69 1.39 Best regards, -- Jo=C3=A3o Paulo Rechi Vita http://about.me/jprvita