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>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/2] tcp: remove tcp_rate.c
Date: Wed, 21 Jan 2026 09:59:21 +0000 [thread overview]
Message-ID: <20260121095923.3134639-1-edumazet@google.com> (raw)
Move tcp_rate_gen() to tcp_input.c and tcp_rate_check_app_limited()
to tcp.c for better code generation.
tcp_rate.c was interesting from code maintenance perspective
but was adding cpu costs.
Eric Dumazet (2):
tcp: move tcp_rate_gen to tcp_input.c
tcp: move tcp_rate_check_app_limited() to tcp.c
include/net/tcp.h | 5 +-
net/ipv4/Makefile | 2 +-
net/ipv4/tcp.c | 18 ++++++
net/ipv4/tcp_input.c | 110 ++++++++++++++++++++++++++++++++++++
net/ipv4/tcp_rate.c | 130 -------------------------------------------
5 files changed, 130 insertions(+), 135 deletions(-)
delete mode 100644 net/ipv4/tcp_rate.c
base-commit: d8f87aa5fa0a4276491fa8ef436cd22605a3f9ba
--
2.52.0.457.g6b5491de43-goog
next reply other threads:[~2026-01-21 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 9:59 Eric Dumazet [this message]
2026-01-21 9:59 ` [PATCH net-next 1/2] tcp: move tcp_rate_gen to tcp_input.c Eric Dumazet
2026-01-21 16:16 ` Neal Cardwell
2026-01-21 9:59 ` [PATCH net-next 2/2] tcp: move tcp_rate_check_app_limited() to tcp.c Eric Dumazet
2026-01-21 16:19 ` Neal Cardwell
2026-01-23 2:40 ` [PATCH net-next 0/2] tcp: remove tcp_rate.c patchwork-bot+netdevbpf
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=20260121095923.3134639-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox