Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4DA23C64EC4 for ; Thu, 9 Mar 2023 09:45:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231394AbjCIJpv (ORCPT ); Thu, 9 Mar 2023 04:45:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37300 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231514AbjCIJpI (ORCPT ); Thu, 9 Mar 2023 04:45:08 -0500 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E721E2C63 for ; Thu, 9 Mar 2023 01:44:33 -0800 (PST) Received: from pps.filterd (m0279862.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3296NKnJ032541; Thu, 9 Mar 2023 09:44:20 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : from : to : cc : references : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=tBxXB2pgDpwC//H7BNTDGgn52qqfudxbt4BZ3rFOoks=; b=XOHQrZzxMkGNJ1tfZLw+AApHU73bLDSsqizsvKuyuIS8B2NpHa3QccOr01Es8tFnvf4V Y3k0QlOSvijoCQw/eP4cBKAmsvHhkJKEQEFmp2Z3jyWVGPOk12fWZPYfh9Goh/kelCij Q7gi69/5UlHn6KRW+ecZohQ1IMl9RGToVjoSUVt+Gxud/mX6zHFigFpGFzf0uasP6j1s WP0vIfF71I1aGKQtHU4UhuYWYJAiYVPvB+fMBj6DjAYEghry6/OVkAG35oQMCoCcPMYK 2YuuhulBNK2CHCmbOxJ62SZPmgHPu8x6l1TtJWhoPclfKOXJUim8nW2nrvgSOuc+nmw5 Zw== Received: from nalasppmta05.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3p6wcmja8r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 09 Mar 2023 09:44:19 +0000 Received: from nalasex01a.na.qualcomm.com (nalasex01a.na.qualcomm.com [10.47.209.196]) by NALASPPMTA05.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 3299i2KX009036 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 9 Mar 2023 09:44:02 GMT Received: from [10.216.30.212] (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.41; Thu, 9 Mar 2023 01:44:00 -0800 Message-ID: Date: Thu, 9 Mar 2023 15:13:57 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH] wifi: ath11k: Optimize 6 GHz scan time Content-Language: en-US From: Manikanta Pubbisetty To: Johannes Berg , James Prestwood , Marcel Holtmann CC: , , References: <20221220043823.20382-1-quic_mpubbise@quicinc.com> <5DAEA8B2-2B44-4A91-9E57-12B6C6B6C1FC@holtmann.org> <2861463e-a097-7efe-bc75-f13c8faf9547@quicinc.com> <378a1d63b3752ace7384c44d6f5184753fa7795d.camel@gmail.com> <0b06dea9-d5be-1edc-62ca-576398d1bcd8@quicinc.com> <0e7644cbfa9e4ba0d534681166ca467ea1684719.camel@gmail.com> <10e4b6bf-f375-e50f-063a-b44471359d25@quicinc.com> <56a3651e48ae621afa4c50f1ba0d9fedeefb2c31.camel@sipsolutions.net> <7ddf99b1-4aef-c950-f61b-ba79ed086095@quicinc.com> In-Reply-To: <7ddf99b1-4aef-c950-f61b-ba79ed086095@quicinc.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01a.na.qualcomm.com (10.47.209.196) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: gqwdTzecJ6Tvcjs9bf9oMQ2nhKMq5s7N X-Proofpoint-ORIG-GUID: gqwdTzecJ6Tvcjs9bf9oMQ2nhKMq5s7N X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-03-09_06,2023-03-08_03,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 malwarescore=0 spamscore=0 adultscore=0 bulkscore=0 mlxlogscore=586 clxscore=1015 priorityscore=1501 lowpriorityscore=0 impostorscore=0 suspectscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2303090077 Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 2/27/2023 9:53 AM, Manikanta Pubbisetty wrote: > On 2/24/2023 3:45 PM, Johannes Berg wrote: >> On Fri, 2023-02-24 at 15:38 +0530, Manikanta Pubbisetty wrote: >>> On 1/10/2023 10:35 PM, James Prestwood wrote: >>>> On Tue, 2023-01-10 at 10:49 +0530, Manikanta Pubbisetty wrote: >>>>> On 12/29/2022 2:52 AM, James Prestwood wrote: >>>>>> Hi Manikanta, >>>>>>> By the way, userspace itself selects the frequencies to scan, not >>>>>>> the >>>>>>> driver. >>>>>>> >>>>>>> If we see the split scan implementation in cfg80211, this is the >>>>>>> how >>>>>>> it >>>>>>> is implemented. If NL80211_SCAN_FLAG_COLOCATED_6GHZ is set, it >>>>>>> selects >>>>>>> all PSC channels and those non-PSC channels where RNR IE >>>>>>> information >>>>>>> is >>>>>>> found in the legacy scan results. If this flag is not set, all >>>>>>> channels >>>>>>> in 6 GHz are included in the scan freq list. It is upto userspace >>>>>>> to >>>>>>> decide what it wants. >>>>>> >>>>>> >>>>>> This isn't your problem, but it needs to be said: >>>>>> >>>>>> The nl80211 docs need and update to reflect this behavior (or >>>>>> remove >>>>>> the PSC logic). IMO this is really weird that the kernel selects >>>>>> PSC's >>>>>> based on the co-located flag. The docs don't describe this behavior >>>>>> and >>>>>> the flag's name is misleading (its not >>>>>> SCAN_FLAG_COLOCATED_AND_PSC_6GHZ) :) >>>>>> >>>>> >>>>> Sorry for the late reply, I was on vacation. >>>>> >>>>> What you said make sense. The existing flag should not add PSC >>>>> channels >>>>> according to the flag description. >>>>> >>>>> We can add another flag something like you pointed out >>>>> SCAN_FLAG_COLOCATED_AND_PSC_6GHZ and include PSC channels if this >>>>> flag >>>>> is set. What do you say? >>>> >>>> I'm no authority here, just wanted to point this out. This is something >>>> that would need to be in mac80211 though, not just a specific driver. >>>> It would be up to the maintainers and would require changing the >>>> behavior of the existing flag, which then changes behavior in >>>> wpa_supplicant/hostapd. So its somewhat intrusive. >>>> >>>> But personally I'd be for it. And just require userspace include PSC's >>>> like any other channels if they need those. >>>> >>> >>> Hi Johannes, >>> >>> What is your opinion on the changes being proposed to the 6 GHz scan in >>> cfg80211 that is being discussed in this thread? >>> >> >> I don't think we can/should change the semantics of an existing flag >> now, but we can certainly update the documentation to match the >> implementation, and add more flags to make it more flexible. >> >> johannes > > Sure, makes sense. I'll make the changes and send them out for review. > Sent out a patch to update the documentation for review. https://patchwork.kernel.org/project/linux-wireless/patch/20230308104556.9399-1-quic_mpubbise@quicinc.com/ Thanks, Manikanta