All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath10k@lists.infradead.org
Cc: "Linus Lüssing" <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>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"Linus Lüssing" <ll@simonwunderlich.de>,
	mail@adrianschmutzler.de
Subject: Re: [PATCH] ath10k: increase rx buffer size to 2048
Date: Sat, 25 Apr 2020 13:14:42 +0200	[thread overview]
Message-ID: <3097447.aZuNXRJysd@sven-edge> (raw)
In-Reply-To: <3300912.TRQvxCK2vZ@bentobox>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

On Wednesday, 1 April 2020 09:00:49 CEST Sven Eckelmann wrote:
> On Wednesday, 5 February 2020 20:10:43 CEST Linus Lüssing wrote:
> > From: Linus Lüssing <ll@simonwunderlich.de>
> > 
> > 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.
> [...]
> 
> @Kalle, I saw that this patch was marked as deferred [1] but I couldn't find 
> any mail why it was done so. It seems like this currently creates real world 
> problems - so would be nice if you could explain shortly what is currently 
> blocking its acceptance.

Ping?

Kind regards,
	Sven

> [1] https://patchwork.kernel.org/patch/11367055/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: ath10k@lists.infradead.org
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>,
	"Simon Wunderlich" <sw@simonwunderlich.de>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, mail@adrianschmutzler.de,
	"Ben Greear" <greearb@candelatech.com>,
	"David S . Miller" <davem@davemloft.net>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"Linus Lüssing" <ll@simonwunderlich.de>
Subject: Re: [PATCH] ath10k: increase rx buffer size to 2048
Date: Sat, 25 Apr 2020 13:14:42 +0200	[thread overview]
Message-ID: <3097447.aZuNXRJysd@sven-edge> (raw)
In-Reply-To: <3300912.TRQvxCK2vZ@bentobox>


[-- Attachment #1.1: Type: text/plain, Size: 941 bytes --]

On Wednesday, 1 April 2020 09:00:49 CEST Sven Eckelmann wrote:
> On Wednesday, 5 February 2020 20:10:43 CEST Linus Lüssing wrote:
> > From: Linus Lüssing <ll@simonwunderlich.de>
> > 
> > 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.
> [...]
> 
> @Kalle, I saw that this patch was marked as deferred [1] but I couldn't find 
> any mail why it was done so. It seems like this currently creates real world 
> problems - so would be nice if you could explain shortly what is currently 
> blocking its acceptance.

Ping?

Kind regards,
	Sven

> [1] https://patchwork.kernel.org/patch/11367055/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2020-04-25 11:14 UTC|newest]

Thread overview: 14+ 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-02-05 19:10 ` Linus Lüssing
2020-04-01  7:00 ` Sven Eckelmann
2020-04-01  7:00   ` Sven Eckelmann
2020-04-25 11:14   ` Sven Eckelmann [this message]
2020-04-25 11:14     ` Sven Eckelmann
2020-04-28 12:01     ` Kalle Valo
2020-04-28 12:01       ` Kalle Valo
2020-04-28 12:27       ` Dave Taht
2020-04-28 12:27         ` Dave Taht
2020-04-28 14:27       ` Ben Greear
2020-04-28 14:27         ` Ben Greear
2021-01-18 16:13 ` Kalle Valo
2021-01-18 16:13 ` 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=3097447.aZuNXRJysd@sven-edge \
    --to=sven@narfation.org \
    --cc=ath10k@lists.infradead.org \
    --cc=davem@davemloft.net \
    --cc=greearb@candelatech.com \
    --cc=kvalo@codeaurora.org \
    --cc=linus.luessing@c0d3.blue \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ll@simonwunderlich.de \
    --cc=mail@adrianschmutzler.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 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.