From: Jakub Kicinski <kuba@kernel.org>
To: John Daley <johndale@cisco.com>
Cc: benve@cisco.com, satishkh@cisco.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/3] enic: Use Page Pool API for receiving packets
Date: Mon, 20 Jan 2025 11:31:59 -0800 [thread overview]
Message-ID: <20250120113159.7386b5bf@kernel.org> (raw)
In-Reply-To: <20250119200018.5522-1-johndale@cisco.com>
On Sun, 19 Jan 2025 12:00:15 -0800 John Daley wrote:
> Use the Page Pool API for RX. The Page Pool API improves bandwidth and
> CPU overhead by recycling pages instead of allocating new buffers in the
> driver. Also, page pool fragment allocation for smaller MTUs is used
> allow multiple packets to share pages.
>
> RX code was moved to its own file and some refactoring was done
> beforehand to make the page pool changes more trasparent and to simplify
> the resulting code.
Sorry to say, we already closed net-next for the 6.14 merge window:
https://lore.kernel.org/r/20250117182059.7ce1196f@kernel.org/
You'll have to repost in 2 weeks.
prev parent reply other threads:[~2025-01-20 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 20:00 [PATCH net-next v7 0/3] enic: Use Page Pool API for receiving packets John Daley
2025-01-19 20:00 ` [PATCH net-next v7 1/3] enic: Move RX functions to their own file John Daley
2025-01-19 20:00 ` [PATCH net-next v7 2/3] enic: Simplify RX handler function John Daley
2025-01-19 20:00 ` [PATCH net-next v7 3/3] enic: Use the Page Pool API for RX John Daley
2025-01-20 19:31 ` 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=20250120113159.7386b5bf@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johndale@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=satishkh@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).