DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CE03F2081C
Message-ID: <b833d8c0987e838759dbf00d97d4989a267a10fb.camel@sipsolutions.net>
Subject: Re: [PATCH 0/4] cfg80211/mac80211: Add support for TID specific
 configuration
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Tamizh chelvam <tamizhr@codeaurora.org>, ath10k@lists.infradead.org
Cc:     linux-wireless@vger.kernel.org,
        Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Date:   Mon, 05 Nov 2018 21:43:48 +0100
In-Reply-To: <1540230918-27712-1-git-send-email-tamizhr@codeaurora.org>
References: <1540230918-27712-1-git-send-email-tamizhr@codeaurora.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Mon, 2018-10-22 at 23:25 +0530, Tamizh chelvam wrote:
> Add infrastructure for per TID aggregation/retry count configurations
> such as retry count and AMPDU aggregation control(disable/enable).
> In some scenario reducing the number of retry count for a specific data
> traffic can reduce the latency by proceeding with the next packet
> instead of retrying the same packet more time. This will be useful
> where the next packet can resume the operation without an issue.

Not sure I understand this, how can you expect to control something on a
per-packet basis using this?

Sergey, looks like your A-MPDU control is already in here per RA/TID,
and A-MSDU could be added easily?

johannes