From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: kabel@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
thomas.petazzoni@bootlin.com
Subject: Re: [PATCH net-next 0/6] net: mvneta: reduce size of TSO header allocation
Date: Thu, 11 May 2023 11:10:22 +0000 [thread overview]
Message-ID: <168380342209.3308.11892374459667294124.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZFtuhJOC03qpASt2@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 10 May 2023 11:14:28 +0100 you wrote:
> Hi,
>
> With reference to
> https://forum.turris.cz/t/random-kernel-exceptions-on-hbl-tos-7-0/18865/
> https://github.com/openwrt/openwrt/pull/12375#issuecomment-1528842334
>
> It appears that mvneta attempts an order-6 allocation for the TSO
> header memory. While this succeeds early on in the system's life time,
> trying order-6 allocations later can result in failure due to memory
> fragmentation.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: mvneta: fix transmit path dma-unmapping on error
https://git.kernel.org/netdev/net-next/c/fef99e840d46
- [net-next,2/5] net: mvneta: mark mapped and tso buffers separately
https://git.kernel.org/netdev/net-next/c/b0bd1b07c3ad
- [net-next,3/5] net: mvneta: use buf->type to determine whether to dma-unmap
https://git.kernel.org/netdev/net-next/c/f00ba4f41acc
- [net-next,4/5] net: mvneta: move tso_build_hdr() into mvneta_tso_put_hdr()
https://git.kernel.org/netdev/net-next/c/d41eb5557668
- [net-next,5/5] net: mvneta: allocate TSO header DMA memory in chunks
https://git.kernel.org/netdev/net-next/c/33f4cefb26e9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-11 11:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 10:14 [PATCH net-next 0/6] net: mvneta: reduce size of TSO header allocation Russell King (Oracle)
2023-05-10 10:15 ` [PATCH net-next 1/5] net: mvneta: fix transmit path dma-unmapping on error Russell King (Oracle)
2023-05-10 11:33 ` Eric Dumazet
2023-05-10 10:15 ` [PATCH net-next 2/5] net: mvneta: mark mapped and tso buffers separately Russell King (Oracle)
2023-05-10 11:34 ` Eric Dumazet
2023-05-10 10:15 ` [PATCH net-next 3/5] net: mvneta: use buf->type to determine whether to dma-unmap Russell King (Oracle)
2023-05-10 11:34 ` Eric Dumazet
2023-05-10 10:15 ` [PATCH net-next 4/5] net: mvneta: move tso_build_hdr() into mvneta_tso_put_hdr() Russell King (Oracle)
2023-05-10 11:34 ` Eric Dumazet
2023-05-10 10:16 ` [PATCH net-next 5/5] net: mvneta: allocate TSO header DMA memory in chunks Russell King (Oracle)
2023-05-10 11:38 ` Eric Dumazet
2023-05-10 11:48 ` Russell King (Oracle)
2023-05-10 12:00 ` Thomas Petazzoni
2023-05-10 10:36 ` [PATCH net-next 0/6] net: mvneta: reduce size of TSO header allocation Russell King (Oracle)
2023-05-11 11:10 ` patchwork-bot+netdevbpf [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=168380342209.3308.11892374459667294124.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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.