linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v7 5/5] wifi: mac80211: add support to call csa_finish on a link
Date: Tue, 30 Jan 2024 16:23:17 +0530	[thread overview]
Message-ID: <a04f47b4-b3fb-4cff-b9de-b7af89f1ff98@quicinc.com> (raw)
In-Reply-To: <e19c796c9ffe3170e34543c95c6d74ced5b1429f.camel@sipsolutions.net>

On 1/30/24 15:51, Johannes Berg wrote:
> On Tue, 2024-01-30 at 10:02 +0530, Aditya Kumar Singh wrote:
>> Currently ieee80211_csa_finish() function finalizes CSA by scheduling a
>> finalizing worker using the deflink. With MLO, there is a need to do it
>> on a given link basis.
>>
>> Add changes to pass link ID of the link on which CSA needs to be finalized.
> 
> Why not just directly say
> 
> "Pass the link ID of ..."
> 
> To me at least it seems obvious that a commit makes changes :)
> 
> Anyway .. I'll stop nit-picking too much about your commit messages I
> guess, and worst case just rephrase them later.
> 
> (I'm kind of working on this area of CSA too right now, though with a
> focus on client.)
> 
>> +	/* TODO: MBSSID with MLO changes */
>>   	if (vif->mbssid_tx_vif == vif) {
> 
> Could you say (even here) more precisely what'd be needed?
> 

We are checking right now "vif->mbssid_tx_vif == vif" for mbssid check. 
However, with MLO, one single vif can have multiple links and among 
those 1 or more could be mbssid enabled. Hence, changes are needed to 
store this mbssid related info on link basis instead of vif directly.

>>   		/* Trigger ieee80211_csa_finish() on the non-transmitting
>>   		 * interfaces when channel switch is received on

Then later where we are iterating over all interfaces, there also we 
need to handle it on link basis. Including all these would make this 
patch a lot bigger. Hence planned to address the whole MBSSID+MLO 
changes in a separate series overall.


>> @@ -3568,7 +3579,7 @@ void ieee80211_csa_finish(struct ieee80211_vif *vif)
>>   					 &iter->deflink.csa_finalize_work);
> 
> that still seems to use deflink there, for sure.
> 

Yeah since MBSSID currently would work without MLO, it is safe to use 
deflink of the non tx vaps while we are iterating.


      reply	other threads:[~2024-01-30 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  4:32 [PATCH v7 0/5] wifi: cfg80211/mac80211: add link_id handling in AP channel switch during Multi-Link Operation Aditya Kumar Singh
2024-01-30  4:32 ` [PATCH v7 1/5] wifi: cfg80211: send link id in channel_switch ops Aditya Kumar Singh
2024-01-30 10:13   ` Johannes Berg
2024-01-30 10:35     ` Aditya Kumar Singh
2024-01-30 10:36       ` Johannes Berg
2024-01-30  4:32 ` [PATCH v7 2/5] wifi: mac80211: update beacon counters per link basis Aditya Kumar Singh
2024-01-30  4:32 ` [PATCH v7 3/5] wifi: mac80211: handle set csa/after_csa beacon on " Aditya Kumar Singh
2024-01-30 10:17   ` Johannes Berg
2024-01-30 10:43     ` Aditya Kumar Singh
2024-01-30 13:50       ` Aditya Kumar Singh
2024-01-30 13:51         ` Johannes Berg
2024-01-30  4:32 ` [PATCH v7 4/5] wifi: mac80211: start and finalize channel switch on " Aditya Kumar Singh
2024-01-30  4:32 ` [PATCH v7 5/5] wifi: mac80211: add support to call csa_finish on a link Aditya Kumar Singh
2024-01-30 10:21   ` Johannes Berg
2024-01-30 10:53     ` Aditya Kumar Singh [this message]

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=a04f47b4-b3fb-4cff-b9de-b7af89f1ff98@quicinc.com \
    --to=quic_adisi@quicinc.com \
    --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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).