Received: by 2002:ac8:156:0:b0:3e0:cd10:60c8 with SMTP id f22csp2670837qtg; Tue, 4 Apr 2023 06:10:51 -0700 (PDT) X-Google-Smtp-Source: AKy350YwUZmcbPEEvjkt7801K4sojUOxNE5/LUUSfI/yd2eWYluKGM79UJ7oGTRbf3uyqLDbaLzY X-Received: by 2002:a17:90b:38cd:b0:234:dc4:2006 with SMTP id nn13-20020a17090b38cd00b002340dc42006mr2977597pjb.4.1680613850911; Tue, 04 Apr 2023 06:10:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680613850; cv=none; d=google.com; s=arc-20160816; b=um2T6m5b4tuSkqMi2GlK1+ulp2IkSLqR8iqAMvzV08T05Fbfq86ntS+GUaNsiooevm 0gn23Do1/lLTq7YyrNziIv0p9Ybgk9KJiZUQlT6HALXWXIcDVzSiRYb3miI5+YjOzeuS 7zFeLWkISoHXZOxEECsiqWSSj0kNNMMLmemVLet0UtTD0HiSm6XLVbj0Ps3cKBisE0oW O0mMT6CRb7gA36Smi3uyVLO4FLozr1ftJeMz4q5PfCLVAjmYeTOl7ByJxBjhtHhpDmck 48TAWS9zurrgyacT87oNu/he3YK9OU5bfwr8soLl4J3RFTEtfCosKQ7nTk4bZFrs1VZ5 4FBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:references :cc:to:from:content-language:subject:user-agent:mime-version:date :message-id:dkim-signature; bh=GQgvbLoGQ9+MFTQvkOnxOVhyLLZ36bQzxEwEEuXoPH4=; b=Mkt/lAv3Iy9HmjvGX/fp7RxbXG4COJS2hHiAhllgRsjhEpC3rLjnE/RxbOPtvurUo4 a2xokeHtCC7vtKPsK9dF9JuZL1c1ZtybYQGG2yx+NHDwX/uyEYnmyoaSsLxBsLrTNKsl Mzqd8WZgoCR2SjYwY4FEeu6RftEMFU4Fsso4NwUF6e9XxxPcip1uw4/oLQ42MWrLzCMF nWqNWrgDyPbXdIQQCBai6zS47RuCjcqggLz1GpivzJuT40K7NawLzYCZCxPdAZIFf9Io y3PV6dPKfa69yTYtP3P4iekOnuS1BiC6+YkyIbUdQPugerzf+aljSv67zUSgmMg1rMny Fg0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@free.fr header.s=smtp-20201208 header.b=sOR0MeTD; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=free.fr Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s15-20020a632c0f000000b00502f4fd0c16si10108882pgs.653.2023.04.04.06.10.43; Tue, 04 Apr 2023 06:10:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@free.fr header.s=smtp-20201208 header.b=sOR0MeTD; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=free.fr Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233852AbjDDMzJ (ORCPT + 59 others); Tue, 4 Apr 2023 08:55:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59872 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234610AbjDDMzG (ORCPT ); Tue, 4 Apr 2023 08:55:06 -0400 Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0A53F3AA4 for ; Tue, 4 Apr 2023 05:54:56 -0700 (PDT) Received: from [192.168.108.81] (unknown [213.36.7.13]) (Authenticated sender: marc.w.gonzalez@free.fr) by smtp2-g21.free.fr (Postfix) with ESMTPSA id 777CA2003DE; Tue, 4 Apr 2023 14:54:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=free.fr; s=smtp-20201208; t=1680612894; bh=S+/zNTMxl4YfEZerK9buqZZCEV+VNnXIqXHpKvSSZd0=; h=Date:Subject:From:To:Cc:References:In-Reply-To:From; b=sOR0MeTDGejKoVMBzlmAIJBzcQ/J59USt8gyT1MunDeacW6XUewYwYSgmQDwEcNrS tCJBgEBSbVZXK3tgMIG8L2i3zdKAaX2RR9UwYxaqzN6M2F5WjEifmrXbQnJFsT4MHW CsRBz86/Szk3gFwymP4QuxI+w26d8P6fTOYAEiqnsCyUJWJ9DCLbuNYwjVHutSJHti JYvEGo17NJYWFXSDdDmMMMnfz27E3mPkRus9QWT1wH2/Y1S6uFwNa0fZC8BjR1ST/f TrZToUOHv71kbXLyxnpKn0C8QsshDxZXVw6wds3RK70PYr0U0hNYHHB65/w1lwWguY Ql2TUDFnldnqg== Message-ID: Date: Tue, 4 Apr 2023 14:54:46 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: [RESEND] Throughput & CPU usage of WiFi download Content-Language: en-US From: Marc Gonzalez To: linux-amlogic@lists.infradead.org, linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com Cc: Arend van Spriel , Franky Lin , Hante Meuleman , Pierre-Hugues Husson , Arnaud Vrac References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NUMERIC_HTTP_ADDR, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,WEIRD_PORT autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org [ Re-sending, because gmail blocks messages with img extension, even within archives Great job Microsoft for inferring file type based on file extension... ] Hello everyone, I've been benchmarking various aspects of an SEI530 board, and wanted to share some of the results with the list. The main objective was to compare WiFi download performance on mainline/BR2 and vendor/android systems. (Mainline system was generated using pop-br2-ext-tree.zip. brcmfmac4359-sdio.* left out for size.) https://pixeldrain.com/u/qH3YotXP HW spec Board: SEI530 (SEI510 variant) SoC: S905X2 WiFi: AP6398SR3-J (SDIO BCM4359/9) Test setup WiFi AP using 5Ghz channels 120 (primary) + 116 (secondary) BENCHMARK = "curl --silent -o /dev/null http://192.168.1.254:8095/fixed/10G" Kernel booted with 1) performance governor (no DVFS) 2) nohlt (keep counting cycles in idle) (Full results at the end) Observations: - vendor system manages 245 Mbps, using 40% CPU - mainline system manages 60 Mbps, using 10% CPU - vendor system limited to 62 Mbps, uses 9% CPU 1) Neil Armstrong mentioned that vendor kernel reaches higher throughput by playing tricks with some pads? (Not sure I understood that well, haven't looked at the code) 2) SDIO is clocked higher on vendor system, but could lead to instabilities on some boards? Interesting possible followups - try clocking SDIO higher on mainline system - measure CPU usage at 120 Mbps, does it scale linearly to 20%? - android curl seems to use smaller buffers? TEST RESULTS -- mainline/BR2 (v6.2) time perf record -a -F 1009 $BENCHMARK perf report -s pid -n --header 10_GB in 1338.127552_s = 59.8_Mbps # Overhead Samples Pid:Command 90.0445% 4863024 0:swapper = IDLE 7.2362% 390807 56:irq/17-ffe03000 1.9282% 104136 59:kworker/u9:0-br 0.6965% 37616 142:curl 0.0722% 3897 114:ksdioirqd/mmc2 0.0168% 908 141:perf -- vendor/android (4.9.180 + vendor patches) time simpleperf record -a -f 1009 $BENCHMARK simpleperf report --sort pid,comm 10_GB in 326.54_s = 245_Mbps Overhead Sample Pid Command 59.43% 680339 0 swapper = IDLE 12.59% 156593 15378 curl 11.42% 136024 4392 dhd_rxf 7.57% 88047 4391 dhd_dpc 2.52% 29977 2094 irq/51-meson-am 1.38% 16467 10541 system_server 0.75% 10394 17 ksoftirqd/1 0.73% 9282 15377 simpleperf 0.60% 9226 6 ksoftirqd/0 0.38% 4701 14865 kworker/0:0 0.14% 2055 29 ksoftirqd/3 0.13% 1636 3411 HwBinder:3411_1 0.13% 1760 23 ksoftirqd/2 0.12% 1484 10782 dmx_data_thread 0.12% 1469 3381 composer@2.3-se 0.10% 1329 15425 Jit thread pool Same benchmark, rate limited to 8 MB/s time simpleperf record -a -f 1009 $BENCHMARK --limit-rate 8M simpleperf report --sort pid,comm 10_GB in 1290.22_s = 62 Mbps Overhead Sample Pid Command 91.68% 3687632 0 swapper = IDLE 2.67% 107057 4392 dhd_rxf 1.90% 74721 4391 dhd_dpc 1.00% 41650 22975 curl 0.70% 29239 10541 system_server 0.68% 27406 2094 irq/51-meson-am 0.58% 24781 22974 simpleperf 0.10% 4222 17 ksoftirqd/1 0.10% 4070 10782 dmx_data_thread