All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jason Baron <jbaron@akamai.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net] net: allow alloc_skb_with_frags() to use MAX_SKB_FRAGS
Date: Wed, 24 Sep 2025 00:00:20 +0000	[thread overview]
Message-ID: <175867202049.1967235.5341414234774872189.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250922191957.2855612-1-jbaron@akamai.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 22 Sep 2025 15:19:57 -0400 you wrote:
> Currently, alloc_skb_with_frags() will only fill (MAX_SKB_FRAGS - 1)
> slots. I think it should use all MAX_SKB_FRAGS slots, as callers of
> alloc_skb_with_frags() will size their allocation of frags based
> on MAX_SKB_FRAGS.
> 
> This issue was discovered via a test patch that sets 'order' to 0
> in alloc_skb_with_frags(), which effectively tests/simulates high
> fragmentation. In this case sendmsg() on unix sockets will fail every
> time for large allocations. If the PAGE_SIZE is 4K, then data_len will
> request 68K or 17 pages, but alloc_skb_with_frags() can only allocate
> 64K in this case or 16 pages.
> 
> [...]

Here is the summary with links:
  - [v2,net] net: allow alloc_skb_with_frags() to use MAX_SKB_FRAGS
    https://git.kernel.org/netdev/net/c/ca9f9cdc4de9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-09-24  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 19:19 [PATCH v2 net] net: allow alloc_skb_with_frags() to use MAX_SKB_FRAGS Jason Baron
2025-09-22 19:57 ` Eric Dumazet
2025-09-24  0:00 ` patchwork-bot+netdevbpf [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=175867202049.1967235.5341414234774872189.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jbaron@akamai.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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 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.