From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Veerendranath Jakkam <quic_vjakkam@quicinc.com>,
johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, quic_usdutt@quicinc.com
Subject: Re: [PATCH v2 1/3] cfg80211: Add NL80211_IFTYPE_MLO_LINK type for MLO links on MLD STA
Date: Wed, 23 Feb 2022 13:39:33 +0100 [thread overview]
Message-ID: <269dcdce-ca21-211f-9f87-bc1dfc7d29b2@broadcom.com> (raw)
In-Reply-To: <1645613200-30221-2-git-send-email-quic_vjakkam@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On 2/23/2022 11:46 AM, Veerendranath Jakkam wrote:
> In contrast, NL80211_IFTYPE_MLO_LINK can't be used to represent AP MLO
> link since an MLD AP must support pre-11be and 11be clients
> simultaneously so each AP MLO link affiliated with AP MLD must also act
> as independent AP for pre-11be clients so each AP MLO link must be
Not just for pre-11be clients. 11be clients can opt-out right?
> represented by NL80211_IFTYPE_AP associated with a separate netdev.
>
> Two link AP MLD representation:
>
> AP MLD
> (netdev + wdev)
> / \
> / \
> wlan0 wlan1
> IFTYPE_AP IFTYPE_AP
> (netdev + wdev) (netdev + wdev)
> | |
> | |
> radio(2G) radio(5G)
So the AP MLD is a new IFTYPE? Earlier discussions were suggesting the
AP MLO links would be bridged, but then there would be only a netdev at
AP MLD level, right?
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2022-02-23 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 10:46 [PATCH v2 0/3] cfg80211: Add MLO Link Device abstraction Veerendranath Jakkam
2022-02-23 10:46 ` [PATCH v2 1/3] cfg80211: Add NL80211_IFTYPE_MLO_LINK type for MLO links on MLD STA Veerendranath Jakkam
2022-02-23 12:39 ` Arend van Spriel [this message]
2022-02-24 3:28 ` Vasanthakumar Thiagarajan
2022-02-24 7:59 ` Veerendranath Jakkam
2022-02-26 19:36 ` Arend Van Spriel
2022-03-11 12:17 ` Johannes Berg
2022-03-17 21:42 ` Jeff Johnson
2022-02-23 10:46 ` [PATCH v2 2/3] cfg80211: Indicate MLO links info in connect/roam events Veerendranath Jakkam
2022-02-23 10:46 ` [PATCH v2 3/3] cfg80211: Add support for key operations on NL80211_IFTYPE_MLO_LINK Veerendranath Jakkam
2022-03-11 12:20 ` Johannes Berg
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=269dcdce-ca21-211f-9f87-bc1dfc7d29b2@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_usdutt@quicinc.com \
--cc=quic_vjakkam@quicinc.com \
/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).