From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: "Simon Horman" <horms@kernel.org>,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Jiri Pirko" <jiri@resnulli.us>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
"Eric Dumazet" <edumazet@google.com>
Subject: [PATCH net-next 0/2] net/sched: refine fq_codel memory limits
Date: Tue, 12 May 2026 09:48:57 +0000 [thread overview]
Message-ID: <20260512094859.3673997-1-edumazet@google.com> (raw)
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.
Eric Dumazet (2):
net: make is_skb_wmem() available to modules
net/sched: fq_codel: local packets no longer count against memory
limit
include/net/sock.h | 12 +++++++++++-
include/net/tcp.h | 1 -
net/core/skbuff.c | 2 +-
net/core/sock.c | 3 +++
net/core/sock_destructor.h | 12 ------------
net/ipv4/inet_fragment.c | 2 --
net/ipv4/tcp_output.c | 1 +
net/sched/sch_fq_codel.c | 2 +-
8 files changed, 17 insertions(+), 18 deletions(-)
delete mode 100644 net/core/sock_destructor.h
--
2.54.0.563.g4f69b47b94-goog
next reply other threads:[~2026-05-12 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 9:48 Eric Dumazet [this message]
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
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=20260512094859.3673997-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox