From: "Rameshkumar Sundaram (QUIC)" <quic_ramess@quicinc.com> To: Johannes Berg <johannes@sipsolutions.net>, "Rameshkumar Sundaram (QUIC)" <quic_ramess@quicinc.com>, "ath11k@lists.infradead.org" <ath11k@lists.infradead.org> Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org> Subject: RE: [PATCH 1/2] nl80211: add support to enable/disable bss color collision detection Date: Mon, 23 Jan 2023 04:57:27 +0000 [thread overview] Message-ID: <DM6PR02MB49372BB7FCB6E31CCAC20E9AE9C89@DM6PR02MB4937.namprd02.prod.outlook.com> (raw) In-Reply-To: <74c57dc34af10537f98f5bb9b6ce80e5676e09b0.camel@sipsolutions.net> > -----Original Message----- > From: Johannes Berg <johannes@sipsolutions.net> > Sent: Thursday, January 19, 2023 7:32 PM > To: Rameshkumar Sundaram (QUIC) <quic_ramess@quicinc.com>; > ath11k@lists.infradead.org > Cc: linux-wireless@vger.kernel.org > Subject: Re: [PATCH 1/2] nl80211: add support to enable/disable bss color > collision detection > > On Mon, 2022-12-26 at 14:03 +0530, Rameshkumar Sundaram wrote: > > As per 802.11ax-2021, STAs shall process BSS Color Change Announcement > > (BCCA) from AP and switch to new color, but some STAs aren't > > processing BCCA from AP and not doing color switch, causing them to > > drop data frames from AP post color change. > > > > Provide an option to disable color collision detection and therefore > > not to do BCCA to mitigate the same from AP. If it's required in case > > where STA supports BCCA handling, then it can enabled in AP using this > > option. > > > > You should probably split this into cfg80211 and mac80211. Sure I will do it. > > Also, this doesn't really seem to make a lot of _sense_ since nothing in the > kernel actually acts on detection of a color collision - hostapd is acting on > that. > > So since you can easily make hostapd ignore the event, why do you even > need this? > Kernel will keep sending collision events until we switch color/disable BSS color Hence wanted to avoid the detection itself. > johannes -- ath11k mailing list ath11k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: "Rameshkumar Sundaram (QUIC)" <quic_ramess@quicinc.com> To: Johannes Berg <johannes@sipsolutions.net>, "Rameshkumar Sundaram (QUIC)" <quic_ramess@quicinc.com>, "ath11k@lists.infradead.org" <ath11k@lists.infradead.org> Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org> Subject: RE: [PATCH 1/2] nl80211: add support to enable/disable bss color collision detection Date: Mon, 23 Jan 2023 04:57:27 +0000 [thread overview] Message-ID: <DM6PR02MB49372BB7FCB6E31CCAC20E9AE9C89@DM6PR02MB4937.namprd02.prod.outlook.com> (raw) In-Reply-To: <74c57dc34af10537f98f5bb9b6ce80e5676e09b0.camel@sipsolutions.net> > -----Original Message----- > From: Johannes Berg <johannes@sipsolutions.net> > Sent: Thursday, January 19, 2023 7:32 PM > To: Rameshkumar Sundaram (QUIC) <quic_ramess@quicinc.com>; > ath11k@lists.infradead.org > Cc: linux-wireless@vger.kernel.org > Subject: Re: [PATCH 1/2] nl80211: add support to enable/disable bss color > collision detection > > On Mon, 2022-12-26 at 14:03 +0530, Rameshkumar Sundaram wrote: > > As per 802.11ax-2021, STAs shall process BSS Color Change Announcement > > (BCCA) from AP and switch to new color, but some STAs aren't > > processing BCCA from AP and not doing color switch, causing them to > > drop data frames from AP post color change. > > > > Provide an option to disable color collision detection and therefore > > not to do BCCA to mitigate the same from AP. If it's required in case > > where STA supports BCCA handling, then it can enabled in AP using this > > option. > > > > You should probably split this into cfg80211 and mac80211. Sure I will do it. > > Also, this doesn't really seem to make a lot of _sense_ since nothing in the > kernel actually acts on detection of a color collision - hostapd is acting on > that. > > So since you can easily make hostapd ignore the event, why do you even > need this? > Kernel will keep sending collision events until we switch color/disable BSS color Hence wanted to avoid the detection itself. > johannes
next prev parent reply other threads:[~2023-01-23 4:57 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-26 8:33 [PATCH 0/2] wifi: Add support to enable/disable bss color collision detection Rameshkumar Sundaram 2022-12-26 8:33 ` Rameshkumar Sundaram 2022-12-26 8:33 ` [PATCH 1/2] nl80211: add " Rameshkumar Sundaram 2022-12-26 8:33 ` Rameshkumar Sundaram 2023-01-19 14:02 ` Johannes Berg 2023-01-19 14:02 ` Johannes Berg 2023-01-19 14:52 ` Nicolas Cavallari 2023-01-19 14:52 ` Nicolas Cavallari 2023-01-19 14:54 ` Johannes Berg 2023-01-19 14:54 ` Johannes Berg 2023-01-19 18:36 ` Lorenzo Bianconi 2023-01-19 18:36 ` Lorenzo Bianconi 2023-01-20 15:55 ` Lorenzo Bianconi 2023-01-20 15:55 ` Lorenzo Bianconi 2023-01-20 16:10 ` Nicolas Cavallari 2023-01-20 16:10 ` Nicolas Cavallari 2023-01-24 11:13 ` Nicolas Cavallari 2023-01-24 11:13 ` Nicolas Cavallari 2023-01-24 14:09 ` Lorenzo Bianconi 2023-01-24 14:09 ` Lorenzo Bianconi 2023-01-23 4:57 ` Rameshkumar Sundaram (QUIC) [this message] 2023-01-23 4:57 ` Rameshkumar Sundaram (QUIC) 2022-12-26 8:33 ` [PATCH 2/2] ath11k: add support to enable/disable BSS " Rameshkumar Sundaram 2022-12-26 8:33 ` Rameshkumar Sundaram
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=DM6PR02MB49372BB7FCB6E31CCAC20E9AE9C89@DM6PR02MB4937.namprd02.prod.outlook.com \ --to=quic_ramess@quicinc.com \ --cc=ath11k@lists.infradead.org \ --cc=johannes@sipsolutions.net \ --cc=linux-wireless@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.