linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Psyborg <pozega.tomislav@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: John Crispin <john@phrozen.org>,
	ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Subject: Re: [RESEND] ath10k: add tx hw 802.11 encapusaltion offloading support
Date: Wed, 18 Dec 2019 21:14:34 +0100	[thread overview]
Message-ID: <CAKR_QVJVfqid8i5PXj3Yg8VJjht=MF2fZg+twkLgEkKuMB2bbQ@mail.gmail.com> (raw)
In-Reply-To: <20191217153000.76AB1C4479C@smtp.codeaurora.org>

On 17/12/2019, Kalle Valo <kvalo@codeaurora.org> wrote:
> John Crispin <john@phrozen.org> wrote:
>
>> 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>
>
> Depends on:
>
> 50ff477a8639 mac80211: add 802.11 encapsulation offloading support
>
> Currently in mac80211-next.
>
> Patch set to Awaiting Upstream.
>
> --
> https://patchwork.kernel.org/patch/11293627/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>

the changeset is missing support for 64bit targets in htt_tx.c

  reply	other threads:[~2019-12-18 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  9:22 [RESEND] ath10k: add tx hw 802.11 encapusaltion offloading support John Crispin
2019-12-17 15:30 ` Kalle Valo
2019-12-18 20:14   ` Tom Psyborg [this message]
2019-12-18 22:45     ` Tom Psyborg
2019-12-18 23:18       ` John Crispin
2019-12-28  3:21         ` Tom Psyborg
2019-12-19  6:36       ` Sebastian Gottschall
2019-12-19 10:31         ` Tom Psyborg
2019-12-19 10:44           ` Sebastian Gottschall
2019-12-19 14:39             ` Tom Psyborg
2020-02-13 16:18     ` Kalle Valo
2019-12-28  4:45 ` Justin Capella

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='CAKR_QVJVfqid8i5PXj3Yg8VJjht=MF2fZg+twkLgEkKuMB2bbQ@mail.gmail.com' \
    --to=pozega.tomislav@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=john@phrozen.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).