Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp3631194pxt; Tue, 10 Aug 2021 07:54:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwxblIZ1jzz3e9v/CuKMP/LBoss21qFITypxBXmRRKRCGqxztbr3QRrtcZLujb+vxmAReRa X-Received: by 2002:a17:906:e0ce:: with SMTP id gl14mr28395290ejb.168.1628607288886; Tue, 10 Aug 2021 07:54:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628607288; cv=none; d=google.com; s=arc-20160816; b=As54EScV0zzD3zeMXofJhJ63POO+XipWi6P38nciKPvcb9BBiKPegUuu4oMf9CrsfO SQSDRfSY3F92XCTyE42Ye6U4Fw7U2gX4CbuFbnB1stXHVHGw9RZPWfXFj2bMFPJEp0N1 eokbvWtDi8Hn7sING3xC3E3rSJT90MeCRxSVxwLpa0M/XnuMD3UN8P1C9efT8BsaK4Z1 eNRf1oW01Uwe0cekqTTXqeWDa6jUHCNNutmJWXrusPnTnj8oufwXHLFP7vNx1uMiA4mW KSKZJtnpl1PMgrn9lwZcQcYzNDDBR+V815y8gBtD2Ai2+CzbGmG/19tmtp26qRQPjlZs crGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=Pq8olG0UKW6uZw5KvpM2GjfJamYM6oRBk+UVQL254Dg=; b=NeBe1MaoLUiKnyyd1Zrgo0y8y0tRueMC1dUiTO0uM6dyY6gBjJf3luVia1d24xzHK0 sscWYyjdLtFTnAanXtRlvYEc5bDA43mMPgiIq2xZ5GAGjs64ccGUpHpMN7tfMeimiglW 18qlNHTdxi42C/i5/375ad1rNHV6sVfbjv624AgqW0VGPBCoOrSZUd1c4WuHZPy74/4U HzWU7WfqB6s+puqxrJs3d+oL6ID8Yundi+8MuVsFtlvSeSrPg5A9mJ5AG32uMPrVclto YJtZTeHA4ViXdE4Rusxm6rhll9W9y7PmSvPuV8DUZPz/TR9b6wBX6MX+ZARhNSdfO7SR X4Cw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@nbd.name header.s=20160729 header.b=JRumlcIK; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q28si7648101edw.278.2021.08.10.07.54.19; Tue, 10 Aug 2021 07:54:48 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@nbd.name header.s=20160729 header.b=JRumlcIK; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240232AbhHJOeN (ORCPT + 99 others); Tue, 10 Aug 2021 10:34:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37062 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239178AbhHJOeN (ORCPT ); Tue, 10 Aug 2021 10:34:13 -0400 Received: from nbd.name (nbd.name [IPv6:2a01:4f8:221:3d45::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DEB03C0613C1 for ; Tue, 10 Aug 2021 07:33:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nbd.name; s=20160729; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Pq8olG0UKW6uZw5KvpM2GjfJamYM6oRBk+UVQL254Dg=; b=JRumlcIKMOZtZcGFcdr9iq3Aon HzC6s1hUJUBr8ZdxTBKYKnwJkIR1ikFna/hQ8MJ3XS4Nx1dBEc7DLfLOoNK1mGeNE6DPkX8vsw6mN l9w5cHvEqGQSnFT2OQfyfZJp+NiWyw2j4Syto10+vJKFIfVXDVV2bKKoFH4Jofot4d8s=; Received: from p4ff13206.dip0.t-ipconnect.de ([79.241.50.6] helo=nf.local) by ds12 with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1mDSp4-0003HS-4s; Tue, 10 Aug 2021 16:33:42 +0200 Subject: Re: [PATCH v5 1/3] nl80211: Add support for beacon tx mode To: Maharaja Kennadyrajan Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org References: <1628585783-21139-1-git-send-email-mkenna@codeaurora.org> <1628585783-21139-2-git-send-email-mkenna@codeaurora.org> <7eaa665c-7f9b-268c-5297-4d3851e10e43@nbd.name> From: Felix Fietkau Message-ID: <92b48724-277c-fc48-a922-6b1d49cd6a71@nbd.name> Date: Tue, 10 Aug 2021 16:33:41 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 2021-08-10 14:02, Maharaja Kennadyrajan wrote: > 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. It still seems to me like something that the driver should detect and handle internally without user configuration, based on number of VAPs and maybe multicast/beacon rate (since the packet duration issue will be worse with CCK rates). - Felix