Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp725084rwd; Mon, 12 Jun 2023 22:27:57 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5mNcx1tGRR+dh06yYjhRMDxk9ZuGwCGahnpC2E6XgBFOYVmFPD4ASyRYOeOLvNRJQK0Lnu X-Received: by 2002:a17:90a:2bc7:b0:25b:fcbb:62ba with SMTP id n7-20020a17090a2bc700b0025bfcbb62bamr2136363pje.45.1686634077714; Mon, 12 Jun 2023 22:27:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686634077; cv=none; d=google.com; s=arc-20160816; b=oFA//pwBfnOa6AxNnAM2d/u4fNcz4hTTLfPj+qDsjbMuHfz2+IomXN3gaRPMQYNsdg cISWA+tVReYXsopwN8SipEoo8z8jV/0h/jHmIU4/QXtsWRePSDTQKMnzc6u56/F9P/r9 KIWiTIJ2J79HpJZd3bnGWRTUHuEvCFtOny1sVE3UwmIJp/60wWnQV4LHqfikalUmPoeT pdm1XAmoQdaHlW93w0pWAkFYPOCBr9UEkbtAtdGV8w76SpXyD/VnIYPtjqblx6h9p8N1 1RGU+GAxPmBErgWHoo5Ia8Hhe9By885hZm0jmcmuIMwOQ82TAo1TvTpo4gtGqfBgNipT 30pA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:in-reply-to :date:references:subject:cc:to:from:dkim-signature; bh=F517odKQF+a5Cn1gkyQJAgwLE75n4qp10tcMUGWsHtM=; b=AW2uuBBDiFDTyF4vVOSWPWP+LlN/WYZwtvXtKaOrR1utum0TGgIP5YTxfgAK1npOaG xAPB32VYRO900P1fWWjvhHakbJAnR22lZ/a6XIV0QLZlbUcEo35PtJovruKePOqz6BbS VHdlghmbNTuz4UQ8x2yAaD8XeZ9rWS9cwTcdYOFOLy3DtF1siziw3K45plj6po/MEoAL qVaYYBKSlWbgcg2O38q4Y3g4J9mFgM393TLsvM3qz8097gnHzEX6DB3OhhEA28za906T 9c5AL1+4ZJItoxtqVHQLw9sDsFThF5wr9BBBYjw3K5CsN7g6/HRQRHT0K7SuPzhZ++I4 xKng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rbAhe7NZ; 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=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q33-20020a17090a4fa400b0025bcf85bda2si3820329pjh.7.2023.06.12.22.27.44; Mon, 12 Jun 2023 22:27:57 -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=@kernel.org header.s=k20201202 header.b=rbAhe7NZ; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238463AbjFMFMw (ORCPT + 61 others); Tue, 13 Jun 2023 01:12:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35582 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232951AbjFMFMu (ORCPT ); Tue, 13 Jun 2023 01:12:50 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9F6EFE62; Mon, 12 Jun 2023 22:12:49 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 3C15261E69; Tue, 13 Jun 2023 05:12:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CF78BC433EF; Tue, 13 Jun 2023 05:12:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1686633168; bh=4kqAAS3SX9JNXmuGjywNhA17eJxvCECeHra6VxQaDBw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=rbAhe7NZu5CJGvuBXPpPG9QRfEHcXU6mWWC3lAqUMgJzZksZaGuq9abalEXyNQYGq hwydWjeaSTHnGfeihlk8Kmug70g1h7hY7vlcCGy91OCznH28V746nwhAY8RT6HZxMp s2Pq9aTX4hi3DPFQBSnRlrM/x32KueeG78qNoPb5g7g/fplZXe+qnav5lGsE/IQMW9 Kd8/aDie78OS+g09yFMTWQNuNMUHjrAAh/wWl0mVa8mcXlJYb4M2yPxkhPYUM68Spd DONz2xi4bc1UsrQZ9oTFlgrGtdWdwj5bNqxIdfHHSSGfp+j00IZDGDJkv+xjyCKcaj svkSn+eGuYPTg== From: Kalle Valo To: Brian Norris Cc: Pin-yen Lin , Amitkumar Karwar , Ganapathi Bhat , Sharvari Harisangam , Xinming Hu , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] wifi: mwifiex: Replace RX workqueues with kthreads References: <20230609103651.313194-1-treapking@chromium.org> <87o7lohq9e.fsf@kernel.org> Date: Tue, 13 Jun 2023 08:12:42 +0300 In-Reply-To: (Brian Norris's message of "Mon, 12 Jun 2023 16:47:17 -0700") Message-ID: <87r0qgdjxx.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Brian Norris writes: > Hi, > > Thanks Pin-yen for most of the investigation here and for pushing the > patch. With some additional information though, I might suggest *not* > landing this patch at the moment. More details appended: > > On Sat, Jun 10, 2023 at 01:41:51AM +0800, Pin-yen Lin wrote: >> I realized that I might have over-simplified the background and the >> impact of this patch... >> >> The short answer to the question is that the throughput improved from >> 100 mbps to 180 mbps. The test was run on ChromeOS's v5.15 kernel >> fork. More detailed test setting is mentioned in [1]. >> >> However, the throughput of the same test case on our v4.19 kernel is >> 320 mbps. That is, we observed a 320 mbps --> 100 mbps regression when >> we tried to update the kernel version. This patch is more like a >> mitigation of the regression. It improves the throughput, even though >> it is still not as good as the older kernel. >> >> That being said, this patch does improve the throughput, so we think >> this patch can be landed into the mainline kernel. >> >> Best regards, >> Pin-yen >> >> [1]: https://lore.kernel.org/all/ZFvpJb9Dh0FCkLQA@google.com/ > > I (we?) was optimistic this would be an improvement (or at least, no > worse) due to some of the reasoning at [1]. And, the work here is just a > single work item, queued repeatedly to the same unbound workqueue. So > conceptually, it shouldn't be much different than a kthread_worker, > except for scheduler details -- where again, we'd think this should be > an improvement, as the scheduler would now better track load for the > task (mwifiex RX) in question. > > But additional testing on other mwifiex-based systems (RK3399 + PCIE > 8997) showed the inverse: some throughput drops on similar benchmarks, > from 110 Mbps to 80 Mbps. (Frankly, both numbers are significantly below > where we might like...) > > Considering we still don't have a full explanation for all the > performance differences we've been seeing (on either test platform), and > that at least one of our platforms showed a (smaller) regression, I > think we might want to do more research before committing to this. Yeah, I agree and I'll drop this. This is a really weird problem, I hope you can get to the bottom of it. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches