From: Maharaja Kennadyrajan <mkenna@codeaurora.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5 1/3] nl80211: Add support for beacon tx mode
Date: Tue, 10 Aug 2021 17:32:15 +0530 [thread overview]
Message-ID: <f96e91618142c34172d12954f2f08ce9@codeaurora.org> (raw)
In-Reply-To: <7eaa665c-7f9b-268c-5297-4d3851e10e43@nbd.name>
On 2021-08-10 15:44, Felix Fietkau wrote:
> On 2021-08-10 10:56, Maharaja Kennadyrajan wrote:
>> User can configure the below beacon tx mode
>> 1. Staggered mode and 2. Burst mode while bring-up the AP
>> or MESH.
>>
>> Beacons can be sent out in burst(continuously in a single shot
>> one after another) or staggered (equally spread out over beacon
>> interval) mode.
>>
>> Set the beacon_tx_mode as 1 for Staggered mode and 2 for
>> burst mode.
> What's the advantage of one over the other? When and why would the user
> choose a different mode other than the default?
>
[Maha]: In the multi-vap scenario and default or staggered mode,
tx failure of the packets will happen if the packets duration
is greater than the beacon interval between the two vaps.
In case of burst mode it works, where during retry it transmits
the packet.
> - Felix
next prev parent reply other threads:[~2021-08-10 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 8:56 [PATCH v5 0/3] Add support to configure beacon tx mode Maharaja Kennadyrajan
2021-08-10 8:56 ` [PATCH v5 1/3] nl80211: Add support for " Maharaja Kennadyrajan
2021-08-10 10:14 ` Felix Fietkau
2021-08-10 12:02 ` Maharaja Kennadyrajan [this message]
2021-08-10 14:33 ` Felix Fietkau
2021-08-10 10:52 ` Sven Eckelmann
2022-03-24 18:10 ` Maharaja Kennadyrajan
2022-03-25 7:26 ` Sven Eckelmann
2021-08-10 15:43 ` Jeff Johnson
2021-08-10 8:56 ` [PATCH v5 2/3] mac80211: " Maharaja Kennadyrajan
2021-08-10 8:56 ` [PATCH v5 3/3] ath11k: " Maharaja Kennadyrajan
2021-08-10 15:54 ` Jeff Johnson
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=f96e91618142c34172d12954f2f08ce9@codeaurora.org \
--to=mkenna@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).