From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>, <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>,
"Pucha Himasekhar Reddy" <himasekharx.reddy.pucha@intel.com>
Subject: Re: [PATCH net] igb: cope with large MAX_SKB_FRAGS.
Date: Mon, 12 Aug 2024 14:47:26 +0200 [thread overview]
Message-ID: <ZroEXqTmTN7dABWY@boxer> (raw)
In-Reply-To: <ZrYIlDqUc9obiyt9@calimero.vinschen.de>
On Fri, Aug 09, 2024 at 02:16:20PM +0200, Corinna Vinschen wrote:
> On Aug 8 20:20, Maciej Fijalkowski wrote:
> > On Wed, Aug 07, 2024 at 06:09:20PM +0200, Maciej Fijalkowski wrote:
> > > On Tue, Aug 06, 2024 at 03:15:31PM -0700, Tony Nguyen wrote:
> > > > 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.
> >
> > Actually from what I currently understand IGB_2K_TOO_SMALL_WITH_PADDING
> > will give us 'true' for case you are addressing so we could reuse it here?
>
> Well, IGB_2K_TOO_SMALL_WITH_PADDING is a constant expression evaluated
> at build time. The SKB_HEAD_ALIGN expression is dynamically computed,
> basically depending on the MTU.
>
> IGB_2K_TOO_SMALL_WITH_PADDING switches from false to true with
> MAX_SKB_FRAGS set to 22 or more.
>
> So with MAX_SKB_FRAGS set to 17, IGB_2K_TOO_SMALL_WITH_PADDING is false,
> while the SKB_HEAD_ALIGN expression is true for MTUs >= 1703.
MTU >= 1703 will trigger the current adapter->max_frame_size >
IGB_MAX_FRAME_BUILD_SKB statement.
>
> With MAX_SKB_FRAGS set to 45, IGB_2K_TOO_SMALL_WITH_PADDING is true,
> the SKB_HEAD_ALIGN expression is true for MTUs >= 1255.
>
> Given that, IGB_2K_TOO_SMALL_WITH_PADDING might be the more careful
> check. Do you want me to send a v2?
Using IGB_2K_TOO_SMALL_WITH_PADDING here aligns it with igb_skb_pad() when
computing headroom, so if you don't mind maybe it will be cleaner to reuse
it?
>
>
> Thanks,
> Corinna
>
prev parent reply other threads:[~2024-08-12 12:47 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
2024-08-08 18:20 ` Maciej Fijalkowski
2024-08-09 12:16 ` Corinna Vinschen
2024-08-12 12:47 ` Maciej Fijalkowski [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=ZroEXqTmTN7dABWY@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 \
/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).