From: Jakub Kicinski <kuba@kernel.org>
To: Fabian Druschke <fdruschke@outlook.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Fabian Druschke <fabian@druschke.network>,
Heiner Kallweit <hkallweit1@gmail.com>,
nic_swsd@realtek.com, "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] r8169: avoid OOM when allocating RX buffers
Date: Tue, 17 Feb 2026 14:33:54 -0800 [thread overview]
Message-ID: <20260217143354.3366db18@kernel.org> (raw)
In-Reply-To: <GVZP280MB1013A39E6B154E88E8CBB87EAF6DA@GVZP280MB1013.SWEP280.PROD.OUTLOOK.COM>
On Tue, 17 Feb 2026 22:50:30 +0100 Fabian Druschke wrote:
> Ahoy! Thanks for clarification! Didn't know it was intended behaviour.
>
> We've encountered this issue specifically with this Realtek NIC on
> ShredOS due to lack of mlx5, mlx4 etc.
>
> For NICs like ixgbe we didn't encounter this issue so i was thinking
> about a bug.
Most / all "professional grade"(??) NICs support scatter, where larger
frames are written into multiple chunks, 4kB each. order-2 allocations
on the fast path are a bad idea. One way to alleviate the performance
implications would be to use page pool, but that doesn't help with the
initial fill, just the datapath :(
reminder: please avoid top posting when replying on the mailing list
prev parent reply other threads:[~2026-02-17 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 18:52 [PATCH] r8169: avoid OOM when allocating RX buffers Fabian Druschke
2026-02-16 19:35 ` Eric Dumazet
2026-02-16 20:13 ` Andrew Lunn
2026-02-17 21:50 ` Fabian Druschke
2026-02-17 22:33 ` Jakub Kicinski [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=20260217143354.3366db18@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabian@druschke.network \
--cc=fdruschke@outlook.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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