Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp7212547rwr; Wed, 10 May 2023 05:35:21 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7hux/OqxmFg8aKKu6WUT8v6u/ktoljT4vwLlW7yyuJmNGjquu7Tvziwv35hSedHaTQTw8M X-Received: by 2002:a05:6a20:431f:b0:dd:b941:5d99 with SMTP id h31-20020a056a20431f00b000ddb9415d99mr23630639pzk.51.1683722121516; Wed, 10 May 2023 05:35:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683722121; cv=none; d=google.com; s=arc-20160816; b=DtDmvRaQqbueFsWtMuceIB0xV22sBSwOJWz5fG7ndIVvYosGNYRdFqvFV32Rm1iASK UUN2n/iFQCPVcjOOChuLexiTVXkEaJPKDEbH7YB59YeErbUafcr9y8DGLy0MLJnnZU+g 1nwIWtKsxLZ4Dd/5wcpewABGcloHB9eVw3xmDQY4Xo+xN6RxduV6tejxAYeoQqBBxLc+ 7WB8PzCUHnVTafyUZ9WsjWkOEAikOkBd4gwRDGzODu1IOlGk0Fdtlca3mP5wcK6ntor3 yznmGjibPNPNtroRNey/7F+oHDZaNQzWezZDioBzRwXIzPKhTsOA/wy2bf1+a9MP+WqK fJ6A== 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 :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=fH86BazKajYWz6GKOtNlQLeQieZJZxHPckvxia2YnZo=; b=GqMDn5fw3TZ/ULlWz3iiHmJmBT/2vUzjY1hhhTaU5uRBrDe+qSusS7p5ykghVIWAYe DMNnhXJzM2vnYFo92DaakrL6vrNkeWLk4GkQiVxF9O/bsYC8NQgBl7iCKOpmRT1fij72 W6xa/nqWl29aPNcAl5bT7CkYhHKSWdqrGn4+Tc/rQJoVdQQ0G3hRcMNawxWphUGUpUP2 BF+yLu7l9NF8ENevF9BPSp60tG3wKmTxuVSH6LT4IbeRGALOQ+++3mL28GcadqywOZOR C+XVt3MYFesSdQh0satTvzhyzTvNMaNvVbAP/sD8sAMftn7PwUeUYj24Q8qanogUR4W9 vUXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=srz3aerL; 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=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k197-20020a633dce000000b0052ca719265dsi3997502pga.874.2023.05.10.05.35.13; Wed, 10 May 2023 05:35:21 -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=@sipsolutions.net header.s=mail header.b=srz3aerL; 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=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236902AbjEJMZn (ORCPT + 61 others); Wed, 10 May 2023 08:25:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60704 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236526AbjEJMZm (ORCPT ); Wed, 10 May 2023 08:25:42 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9DBFA1BD for ; Wed, 10 May 2023 05:25:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=fH86BazKajYWz6GKOtNlQLeQieZJZxHPckvxia2YnZo=; t=1683721541; x=1684931141; b=srz3aerLnh+WKH1iLz2U4uGOYuCTKkda8xPhPF8Hytcas/Y ZhOpsSW4VJZcjRLjzrQgraBIoTp0xTPLEJ+gNPp5olIrb1n+c88154wT1mdilLXedPInp6UkKCB4w berEA3KsweEgpBqT8TL2u3CUtDcCrfAblVFcoZo17FvLY60J4nZ1tzUgDfoAzztoSRmtWH/jyU6sA jbsewgfT6yYVz7o0MyoirzsEaF7iLgVyOXrZejtOc6kTW9xBoptwVjYwqThIRQ+9uan79DBKT+DJB 1kRhvjbXbz3u/D0fHRF+sCzbCoD7kvmyIBXcncmeq0RiRQ1EVDwgKAtHo2v+3xDw==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1pwit0-005OZF-1y; Wed, 10 May 2023 14:25:38 +0200 Message-ID: Subject: Re: [PATCH 10/27] wifi: mac80211: isolate driver from inactive links From: Johannes Berg To: Wen Gong , linux-wireless@vger.kernel.org Cc: ath11k@lists.infradead.org Date: Wed, 10 May 2023 14:25:37 +0200 In-Reply-To: References: <20220902141259.377789-1-johannes@sipsolutions.net> <20220902161143.5ce3dad3be7c.I92e9f7a6c120cd4a3631baf486ad8b6aafcd796f@changeid> <5d82e564-86bf-c26b-077a-d0bc14e2d3c3@quicinc.com> <74f3eb848326607b15336c31a02bdd861ccafb47.camel@sipsolutions.net> <5e3ec5f8-1462-5de6-2b5a-4cf62f23deb7@quicinc.com> <0e7023062f44d0ea68625c27cb13731d17857311.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 On Wed, 2023-05-10 at 20:25 +0800, Wen Gong wrote: > On 5/10/2023 7:24 PM, Johannes Berg wrote: > > On Wed, 2023-05-10 at 19:06 +0800, Wen Gong wrote: > > > On 4/11/2023 3:38 PM, Johannes Berg wrote: > > > > On Tue, 2023-04-04 at 11:28 +0800, Wen Gong wrote: > > > > > May I also add a field such as "u16 active_links_count" in struct > > > > > wiphy_iftype_ext_capab, > > > > > and add logic in function ieee80211_set_vif_links_bitmaps() for s= tation > > > > > like this ?: > > > > > if (active_links_count && hweight16(links) <=3D active_links_coun= t) > > > > > =C2=A0=C2=A0=C2=A0 then sdata->vif.active_links =3D links; > > > > >=20 > > > > Also here, not sure it makes sense in cfg80211 level? > > > >=20 > > > > Though I'm not sure what the idea here is at all - you can refuse t= o > > > > link switch etc, what would you use this for? > > > >=20 > > > > Then again, we haven't really designed out all the link selection s= tuff, > > > > do we want wpa_s to do it, driver to do it, etc.? Hence debugfs. So > > > > depending on what end up doing there, we will obviously need to > > > > advertise some level of link-concurrency to userspace. > > > So will you plan to do something to let wpa_s/userspace app > > > active/deactive links? > > >=20 > > > Or you already have implemented that? > > >=20 > > No plans right now, and honestly not sure what the right thing even is. > OK. For "advertise some level of link-concurrency to userspace", do you= =20 > have any plan/idea? No, not really. johannes >=20