From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
toke@toke.dk, netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] net/sched: refine fq_codel memory limits
Date: Thu, 14 May 2026 02:30:08 +0000 [thread overview]
Message-ID: <177872580830.3927681.5359587387484533956.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260512094859.3673997-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 12 May 2026 09:48:57 +0000 you wrote:
> Packets that are associated with local sockets sk_wmem_alloc
> do not really need additional memory control.
>
> First patch makes is_skb_wmem() available to modules.
>
> Second patch uses is_skb_wmem() in fq_codel.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: make is_skb_wmem() available to modules
https://git.kernel.org/netdev/net-next/c/f0de88303d5e
- [net-next,2/2] net/sched: fq_codel: local packets no longer count against memory limit
https://git.kernel.org/netdev/net-next/c/150061a20651
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-14 2:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 9:48 [PATCH net-next 0/2] net/sched: refine fq_codel memory limits Eric Dumazet
2026-05-12 9:48 ` [PATCH net-next 1/2] net: make is_skb_wmem() available to modules Eric Dumazet
2026-05-12 12:06 ` Toke Høiland-Jørgensen
2026-05-12 9:48 ` [PATCH net-next 2/2] net/sched: fq_codel: local packets no longer count against memory limit Eric Dumazet
2026-05-12 12:11 ` Toke Høiland-Jørgensen
2026-05-12 17:50 ` Eric Dumazet
2026-05-12 18:15 ` Toke Høiland-Jørgensen
2026-05-14 8:24 ` Paolo Abeni
2026-05-14 8:49 ` Eric Dumazet
2026-05-14 9:00 ` Eric Dumazet
2026-05-14 10:06 ` Paolo Abeni
2026-05-15 22:28 ` Victor Nogueira
2026-05-14 2:30 ` 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=177872580830.3927681.5359587387484533956.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@toke.dk \
/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.