From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH 0/2] Support hash based reo destination ring selection
Date: Fri, 14 Feb 2020 15:05:17 +0200 [thread overview]
Message-ID: <87pnehqpyq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1581676286-13265-1-git-send-email-srirrama@codeaurora.org> (Sriram R.'s message of "Fri, 14 Feb 2020 16:01:24 +0530")
Sriram R <srirrama@codeaurora.org> writes:
> Currently, reo destination ring selection is based on pdev,
> i.e each pdev is allocated a static reo destintaion ring and
> rx packets for the pdev is always received on the ring.
> This allows use of only 3 out of 4 reo destination rings at the
> max when all pdev's are active and when only one pdev is active
> we utilize only one ring and other 3 rings remain idle.
> To make effective use of all the reo rings, this patchset enables
> hash based reo destination ring selection where the hash is computed
> based on the 5-tuple ( src/dst ip, src/dst port, protocol) info
> from each packet and is used by hw for destination ring selection.
>
> Also, current implementation of amsdu list based processing is replaced
> with per msdu based handling since the received subframe could be
> pushed to different rings after decap based on hash value computed.
>
> This patchset is based on patchset "ath11k: offload PN verification to the HW"
>
> Sriram R (2):
> ath11k: Configure hash based reo destination ring selection
> ath11k: Perform per-msdu rx processing
You need to CC linux-wireless, so please resend as v2.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2020-02-14 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 10:31 [PATCH 0/2] Support hash based reo destination ring selection Sriram R
2020-02-14 10:31 ` [PATCH 1/2] ath11k: Configure " Sriram R
2020-02-14 10:31 ` [PATCH 2/2] ath11k: Perform per-msdu rx processing Sriram R
2020-02-14 13:05 ` Kalle Valo [this message]
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=87pnehqpyq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=srirrama@codeaurora.org \
/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