From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <netdev@vger.kernel.org>,
Jan Tluka <jtluka@redhat.com>, Jirka Hladky <jhladky@redhat.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Corinna Vinschen <vinschen@redhat.com>,
"Pucha Himasekhar Reddy" <himasekharx.reddy.pucha@intel.com>
Subject: Re: [PATCH net] igb: cope with large MAX_SKB_FRAGS.
Date: Wed, 7 Aug 2024 18:09:20 +0200 [thread overview]
Message-ID: <ZrOcMAhE2RAWL8HB@boxer> (raw)
In-Reply-To: <20240806221533.3360049-1-anthony.l.nguyen@intel.com>
On Tue, Aug 06, 2024 at 03:15:31PM -0700, Tony Nguyen wrote:
> From: Paolo Abeni <pabeni@redhat.com>
>
> Sabrina reports that the igb driver does not cope well with large
> MAX_SKB_FRAG values: setting MAX_SKB_FRAG to 45 causes payload
> corruption on TX.
>
> An easy reproducer is to run ssh to connect to the machine. With
> MAX_SKB_FRAGS=17 it works, with MAX_SKB_FRAGS=45 it fails.
any splat?
>
> The root cause of the issue is that the driver does not take into
> account properly the (possibly large) shared info size when selecting
> the ring layout, and will try to fit two packets inside the same 4K
> page even when the 1st fraglist will trump over the 2nd head.
>
> Address the issue forcing the driver to fit a single packet per page,
> leaving there enough room to store the (currently) largest possible
> skb_shared_info.
>
> Fixes: 3948b05950fd ("net: introduce a config option to tweak MAX_SKB_FRAGS")
> Reported-by: Jan Tluka <jtluka@redhat.com>
> Reported-by: Jirka Hladky <jhladky@redhat.com>
> Reported-by: Sabrina Dubroca <sd@queasysnail.net>
Where was this reported?
> Tested-by: Sabrina Dubroca <sd@queasysnail.net>
> Tested-by: Corinna Vinschen <vinschen@redhat.com>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> Reviewed-by: Eric Dumazet <edumazet@google.com>
> Tested-by: Pucha Himasekhar Reddy <himasekharx.reddy.pucha@intel.com> (A Contingent worker at Intel)
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> iwl-net: https://lore.kernel.org/intel-wired-lan/20240718085633.1285322-1-vinschen@redhat.com/
>
> drivers/net/ethernet/intel/igb/igb_main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c
> index 11be39f435f3..232d6cb836a9 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -4808,6 +4808,7 @@ static void igb_set_rx_buffer_len(struct igb_adapter *adapter,
>
> #if (PAGE_SIZE < 8192)
> if (adapter->max_frame_size > IGB_MAX_FRAME_BUILD_SKB ||
> + SKB_HEAD_ALIGN(adapter->max_frame_size) > (PAGE_SIZE / 2) ||
We should address IGB_2K_TOO_SMALL_WITH_PADDING for this case. I'll think
about it tomorrow.
> rd32(E1000_RCTL) & E1000_RCTL_SBP)
> set_ring_uses_large_buffer(rx_ring);
> #endif
> --
> 2.42.0
>
>
next prev parent reply other threads:[~2024-08-07 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 22:15 [PATCH net] igb: cope with large MAX_SKB_FRAGS Tony Nguyen
2024-08-07 16:09 ` Maciej Fijalkowski [this message]
2024-08-08 18:20 ` Maciej Fijalkowski
2024-08-09 12:16 ` Corinna Vinschen
2024-08-12 12:47 ` Maciej Fijalkowski
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=ZrOcMAhE2RAWL8HB@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=himasekharx.reddy.pucha@intel.com \
--cc=jhladky@redhat.com \
--cc=jtluka@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=vinschen@redhat.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).