From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
Srini Kode <skode@qti.qualcomm.com>,
Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
Shashidhar Lakkavalli <slakkavalli@datto.com>,
Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Subject: Re: [RFC V4 2/2] ath10k: add tx hw 802.11 encapusaltion offloading support
Date: Wed, 10 Apr 2019 18:31:39 +0300 [thread overview]
Message-ID: <87ef69yizo.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20190410073514.12794-3-john@phrozen.org> (John Crispin's message of "Wed, 10 Apr 2019 09:35:14 +0200")
John Crispin <john@phrozen.org> writes:
> From: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
>
> This patch adds support for ethernet rxtx mode to the driver. The feature
> is enabled via a new module parameter. If enabled to driver will enable
> the feature on a per vif basis if all other requirements were met.
>
> Testing on a IPQ4019 based hardware shows a increase in TCP throughput
> of ~20% when the feature is enabled.
>
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
> Signed-off-by: John Crispin <john@phrozen.org>
Looks good to me.
BTW, for ath10k patches (patchsets including ath10k patches) please try
to CC also the ath10k list. Easier to find ath10k patches that way.
--
Kalle Valo
next prev parent reply other threads:[~2019-04-10 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 7:35 [RFC V4 0/2] mac80211: add 802.11 encapsulation offloading John Crispin
2019-04-10 7:35 ` [RFC V4 1/2] mac80211: add hw 80211 encapsulation offloading support John Crispin
2019-04-12 11:37 ` Johannes Berg
2019-04-10 7:35 ` [RFC V4 2/2] ath10k: add tx hw 802.11 encapusaltion " John Crispin
2019-04-10 15:31 ` Kalle Valo [this message]
2019-04-11 18:36 ` John Crispin
2019-04-12 3:56 ` 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=87ef69yizo.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@qti.qualcomm.com \
--cc=skode@qti.qualcomm.com \
--cc=slakkavalli@datto.com \
--cc=vthiagar@qti.qualcomm.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.