Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org E244DC433D2
From:   Kalle Valo <kvalo@codeaurora.org>
To:     Sven Eckelmann <sven@narfation.org>
Cc:     ath10k@lists.infradead.org,
        Linus =?utf-8?Q?L=C3=BCssing?= <linus.luessing@c0d3.blue>,
        Simon Wunderlich <sw@simonwunderlich.de>,
        netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
        linux-kernel@vger.kernel.org, Ben Greear <greearb@candelatech.com>,
        "David S . Miller" <davem@davemloft.net>,
        Linus =?utf-8?Q?L=C3=BCssing?= <ll@simonwunderlich.de>,
        mail@adrianschmutzler.de
Subject: Re: [PATCH] ath10k: increase rx buffer size to 2048
In-Reply-To: <3097447.aZuNXRJysd@sven-edge> (Sven Eckelmann's message of "Sat,
        25 Apr 2020 13:14:42 +0200")
References: <20200205191043.21913-1-linus.luessing@c0d3.blue>
        <3300912.TRQvxCK2vZ@bentobox> <3097447.aZuNXRJysd@sven-edge>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Date:   Tue, 28 Apr 2020 15:01:28 +0300
Message-ID: <87blnblsyv.fsf@codeaurora.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Sven Eckelmann <sven@narfation.org> writes:

> On Wednesday, 1 April 2020 09:00:49 CEST Sven Eckelmann wrote:
>> On Wednesday, 5 February 2020 20:10:43 CEST Linus L=C3=BCssing wrote:
>> > From: Linus L=C3=BCssing <ll@simonwunderlich.de>
>> >=20
>> > Before, only frames with a maximum size of 1528 bytes could be
>> > transmitted between two 802.11s nodes.
>> >=20
>> > 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.
>> >=20
>> > This patch now increases the maxmimum frame size from 1528 to 1656
>> > bytes.
>> [...]
>>=20
>> @Kalle, I saw that this patch was marked as deferred [1] but I couldn't =
find=20
>> any mail why it was done so. It seems like this currently creates real w=
orld=20
>> problems - so would be nice if you could explain shortly what is current=
ly=20
>> blocking its acceptance.
>
> Ping?

Sorry for the delay, my plan was to first write some documentation about
different hardware families but haven't managed to do that yet.

My problem with this patch is that I don't know what hardware and
firmware versions were tested, so it needs analysis before I feel safe
to apply it. The ath10k hardware families are very different that even
if a patch works perfectly on one ath10k hardware it could still break
badly on another one.

What makes me faster to apply ath10k patches is to have comprehensive
analysis in the commit log. This shows me the patch author has
considered about all hardware families, not just the one he is testing
on, and that I don't need to do the analysis myself.

--=20
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatc=
hes