From: Kalle Valo <kvalo@codeaurora.org>
To: Peter Oh <peter.oh@eero.com>
Cc: linux-wireless@vger.kernel.org,
Karthikeyan Periyasamy <periyasa@codeaurora.org>,
ath11k@lists.infradead.org
Subject: Re: [PATCH v2] ath11k: Update tx descriptor search index properly
Date: Tue, 09 Feb 2021 09:22:39 +0200 [thread overview]
Message-ID: <87k0rhvh6o.fsf@codeaurora.org> (raw)
In-Reply-To: <e6d1aaea-8410-3cfb-3308-4722ca8e91ea@eero.com> (Peter Oh's message of "Wed, 3 Feb 2021 22:10:26 -0800")
Peter Oh <peter.oh@eero.com> writes:
> On 2/3/21 7:56 PM, Karthikeyan Periyasamy wrote:
>> Tx descriptor search index field should be updated with hw peer id
>> and not by AST Hash as per the HW/FW recommendation. Incorrect search
>> index causes throughput degradation in all scenario for all the
>> platforms. so updated the search index field with hw peer id, which
>> is a common change applicable for all the platforms. Also no need of these
>> configuration for non station type. seen 10% throughput increase in WDS
>> traffic with this change.
>>
>> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1-01492-QCAHKSWPL_SILICONZ-1
>>
>> Signed-off-by: Karthikeyan Periyasamy <periyasa@codeaurora.org>
>
> Thank you for the details.
BTW after you have reviewed the patch, and you think the patch is ok,
you could reply with:
Reviewed-by: Peter Oh <peter.oh@eero.com>
Patchwork automatically picks up that and then it would be an indication
for me that the patch is ready to be applied. I like the Reviewed-by tag
a lot as then I can see that others have also reviewed the patch.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Peter Oh <peter.oh@eero.com>
Cc: Karthikeyan Periyasamy <periyasa@codeaurora.org>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] ath11k: Update tx descriptor search index properly
Date: Tue, 09 Feb 2021 09:22:39 +0200 [thread overview]
Message-ID: <87k0rhvh6o.fsf@codeaurora.org> (raw)
In-Reply-To: <e6d1aaea-8410-3cfb-3308-4722ca8e91ea@eero.com> (Peter Oh's message of "Wed, 3 Feb 2021 22:10:26 -0800")
Peter Oh <peter.oh@eero.com> writes:
> On 2/3/21 7:56 PM, Karthikeyan Periyasamy wrote:
>> Tx descriptor search index field should be updated with hw peer id
>> and not by AST Hash as per the HW/FW recommendation. Incorrect search
>> index causes throughput degradation in all scenario for all the
>> platforms. so updated the search index field with hw peer id, which
>> is a common change applicable for all the platforms. Also no need of these
>> configuration for non station type. seen 10% throughput increase in WDS
>> traffic with this change.
>>
>> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1-01492-QCAHKSWPL_SILICONZ-1
>>
>> Signed-off-by: Karthikeyan Periyasamy <periyasa@codeaurora.org>
>
> Thank you for the details.
BTW after you have reviewed the patch, and you think the patch is ok,
you could reply with:
Reviewed-by: Peter Oh <peter.oh@eero.com>
Patchwork automatically picks up that and then it would be an indication
for me that the patch is ready to be applied. I like the Reviewed-by tag
a lot as then I can see that others have also reviewed the patch.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-02-09 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 3:56 [PATCH v2] ath11k: Update tx descriptor search index properly Karthikeyan Periyasamy
2021-02-04 3:56 ` Karthikeyan Periyasamy
2021-02-04 6:10 ` Peter Oh
2021-02-04 6:10 ` Peter Oh
2021-02-09 7:22 ` Kalle Valo [this message]
2021-02-09 7:22 ` Kalle Valo
2021-02-09 7:23 ` Kalle Valo
2021-02-09 7:23 ` Kalle Valo
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=87k0rhvh6o.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=periyasa@codeaurora.org \
--cc=peter.oh@eero.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.