From: Kalle Valo <kvalo@codeaurora.org>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: ath10k@lists.infradead.org,
"David S . Miller" <davem@davemloft.net>,
"Ben Greear" <greearb@candelatech.com>,
"Simon Wunderlich" <sw@simonwunderlich.de>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Linus Lüssing" <ll@simonwunderlich.de>
Subject: Re: [PATCH] ath10k: increase rx buffer size to 2048
Date: Mon, 18 Jan 2021 16:13:13 +0000 (UTC) [thread overview]
Message-ID: <20210118161313.0F041C43464@smtp.codeaurora.org> (raw)
In-Reply-To: <20200205191043.21913-1-linus.luessing@c0d3.blue>
Linus Lüssing <linus.luessing@c0d3.blue> wrote:
> Before, only frames with a maximum size of 1528 bytes could be
> transmitted between two 802.11s nodes.
>
> For batman-adv for instance, which adds its own header to each frame,
> we typically need an MTU of at least 1532 bytes to be able to transmit
> without fragmentation.
>
> This patch now increases the maxmimum frame size from 1528 to 1656
> bytes.
>
> Tested with two ath10k devices in 802.11s mode, as well as with
> batman-adv on top of 802.11s with forwarding disabled.
>
> Fix originally found and developed by Ben Greear.
>
> Link: https://github.com/greearb/ath10k-ct/issues/89
> Link: https://github.com/greearb/ath10k-ct/commit/9e5ab25027e0971fa24ccf93373324c08c4e992d
> Cc: Ben Greear <greearb@candelatech.com>
> Signed-off-by: Linus Lüssing <ll@simonwunderlich.de>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
3e6b9cf534ca ath10k: increase rx buffer size to 2048
--
https://patchwork.kernel.org/project/linux-wireless/patch/20200205191043.21913-1-linus.luessing@c0d3.blue/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-01-18 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 19:10 [PATCH] ath10k: increase rx buffer size to 2048 Linus Lüssing
2020-04-01 7:00 ` Sven Eckelmann
2020-04-25 11:14 ` Sven Eckelmann
2020-04-28 12:01 ` Kalle Valo
2020-04-28 12:27 ` Dave Taht
2020-04-28 14:27 ` Ben Greear
2021-01-18 16:13 ` 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=20210118161313.0F041C43464@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ll@simonwunderlich.de \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
/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).