From: Jakub Kicinski <kuba@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: "Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Myeonghun Pak" <mhun512@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: ethernet: cortina: Use page_pool for Gemini RX buffers
Date: Wed, 23 Sep 2026 18:28:30 -0700 [thread overview]
Message-ID: <20260923182830.4f9ddc2a@kernel.org> (raw)
In-Reply-To: <20260920-gemini-ethernet-fixes-3-v1-0-3a2a50a83d89@kernel.org>
On Sun, 20 Sep 2026 22:48:50 +0200 Linus Walleij wrote:
> The Gemini ethernet has this really convoluted queue mechanism using
> a custom queue.
>
> Move the Gemini RX buffer management to a parent-owned page_pool.
TBH sounds like weird piece of HW. IDK if we want to burden the generic
page pool code with weird, 20+ yo drivers+HW :/ Well, I know that
I definitely don't, I don't know if others agree :)
Looks like AI has found plenty o'bugs.
Also, please never put Fixes tags from Linus's tree on net-next patches.
Either net or not a fix.
--
pw-bot: cr
next prev parent reply other threads:[~2026-09-24 1:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 20:48 [PATCH net-next 0/3] net: ethernet: cortina: Use page_pool for Gemini RX buffers Linus Walleij
2026-09-20 20:48 ` [PATCH net-next 1/3] net: ethernet: cortina: Keep shared free queue parent-owned Linus Walleij
2026-09-22 18:51 ` netdev-bot+sashiko
2026-09-20 20:48 ` [PATCH net-next 2/3] net: ethernet: cortina: Manage RX buffers with page_pool Linus Walleij
2026-09-22 18:51 ` netdev-bot+sashiko
2026-09-20 20:48 ` [PATCH net-next 3/3] net: ethernet: cortina: Scale Gemini RX queues to system memory Linus Walleij
2026-09-24 1:28 ` Jakub Kicinski [this message]
2026-09-24 7:40 ` [PATCH net-next 0/3] net: ethernet: cortina: Use page_pool for Gemini RX buffers Linus Walleij
2026-09-24 15:58 ` Jakub Kicinski
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=20260923182830.4f9ddc2a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linusw@kernel.org \
--cc=mhun512@gmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ulli.kroll@googlemail.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.