From: Michal Kubiak <michal.kubiak@intel.com>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>,
<maciej.fijalkowski@intel.com>, <aleksander.lobakin@intel.com>,
<larysa.zaremba@intel.com>, <netdev@vger.kernel.org>,
<przemyslaw.kitszel@intel.com>, <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/3] ice: drop page splitting and recycling
Date: Thu, 31 Jul 2025 18:32:43 +0200 [thread overview]
Message-ID: <aIuaq72FjtkEKRDr@localhost.localdomain> (raw)
In-Reply-To: <2f53087a-3c71-4844-a5e7-9d01dae0d6e9@intel.com>
On Thu, Jul 31, 2025 at 09:17:51AM -0700, Jacob Keller wrote:
>
>
> On 7/31/2025 8:56 AM, Michal Kubiak wrote:
> > On Mon, Jul 07, 2025 at 03:48:36PM -0700, Jacob Keller wrote:
> >>
> >>
> >> On 7/4/2025 9:18 AM, Michal Kubiak wrote:
> >>> @@ -1100,14 +994,10 @@ static void ice_put_rx_mbuf(struct ice_rx_ring *rx_ring, struct xdp_buff *xdp,
> >>> for (i = 0; i < post_xdp_frags; i++) {
> >>> buf = &rx_ring->rx_buf[idx];
> >>>
> >>> - if (verdict & (ICE_XDP_TX | ICE_XDP_REDIR)) {
> >>> - ice_rx_buf_adjust_pg_offset(buf, xdp->frame_sz);
> >>> + if (verdict & (ICE_XDP_TX | ICE_XDP_REDIR))
> >>> *xdp_xmit |= verdict;
> >>> - } else if (verdict & ICE_XDP_CONSUMED) {
> >>> + else if (verdict & ICE_XDP_CONSUMED)
> >>> buf->pagecnt_bias++;
> >>
> >> Why do we still keep pagecnt_bias++ here?
> >
> > My mistake. You're right - as I checked, we never use pagecnt_bias after
> > applying this patch.
> > I will remove pagecnt_bias completely in v2.
> >
> > Thanks,
> > Michal
> >
>
> I think Olek was also aware of this, but please make sure the v2 has
> fixed the errors with 9K MTU as well :D
Sure! I've already synced with Olek about the large MTU regression.
BTW, thanks for your report and detailed testing. TBH, I didn't run the
iperf with 9K MTU before. :)
Before sending the v2, I'll definitely test it the way you suggested.
next prev parent reply other threads:[~2025-07-31 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 16:18 [PATCH iwl-next 0/3] ice: convert Rx path to Page Pool Michal Kubiak
2025-07-04 16:18 ` [PATCH iwl-next 1/3] ice: remove legacy Rx and construct SKB Michal Kubiak
2025-07-04 16:18 ` [PATCH iwl-next 2/3] ice: drop page splitting and recycling Michal Kubiak
2025-07-07 22:48 ` [Intel-wired-lan] " Jacob Keller
2025-07-31 15:56 ` Michal Kubiak
2025-07-31 16:17 ` Jacob Keller
2025-07-31 16:32 ` Michal Kubiak [this message]
2025-07-04 16:18 ` [PATCH iwl-next 3/3] ice: switch to Page Pool Michal Kubiak
2025-07-07 22:58 ` [Intel-wired-lan] " Jacob Keller
2025-08-08 11:40 ` Michal Kubiak
2025-08-08 12:03 ` Paul Menzel
2025-08-08 13:04 ` Michal Kubiak
2025-08-08 13:08 ` Paul Menzel
2025-08-08 16:07 ` Michal Kubiak
2025-07-04 17:05 ` [PATCH iwl-next 0/3] ice: convert Rx path " Michal Kubiak
2025-07-07 23:32 ` [Intel-wired-lan] " Jacob Keller
2025-07-07 23:36 ` Jacob Keller
2025-07-10 22:43 ` Jacob Keller
2025-07-14 14:35 ` Alexander Lobakin
2025-08-08 12:53 ` Michal Kubiak
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=aIuaq72FjtkEKRDr@localhost.localdomain \
--to=michal.kubiak@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=larysa.zaremba@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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).