From: Jason Xing <kerneljasonxing@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org
Cc: netdev@vger.kernel.org, kerneljasonxing@gmail.com,
Jason Xing <kernelxing@tencent.com>
Subject: [PATCH net-next v3 0/6] introduce dropreasons in tcp receive path
Date: Mon, 12 Feb 2024 17:28:21 +0800 [thread overview]
Message-ID: <20240212092827.75378-1-kerneljasonxing@gmail.com> (raw)
From: Jason Xing <kernelxing@tencent.com>
As titled said, we're going to refine the NOT_SPECIFIED reason in the
tcp v4/6 receive fast path.
This serie is another one of the v2 patchset[1] which are here split
into six patches. Besides, this patch is made on top of the previous
serie[2] I submitted some time ago.
[1]
Link: https://lore.kernel.org/all/20240209061213.72152-3-kerneljasonxing@gmail.com/
[2]
Link: https://lore.kernel.org/all/20240212052513.37914-1-kerneljasonxing@gmail.com/
v3:
Link: https://lore.kernel.org/all/CANn89iK40SoyJ8fS2U5kp3pDruo=zfQNPL-ppOF+LYaS9z-MVA@mail.gmail.com/
1. Split that patch into some smaller ones as suggested by Eric.
v2:
Link: https://lore.kernel.org/all/20240204104601.55760-1-kerneljasonxing@gmail.com/
1. change the title of 2/2 patch.
2. fix some warnings checkpatch tool showed before.
3. use return value instead of adding more parameters suggested by Eric.
Jason Xing (6):
tcp: introduce another three dropreasons in receive path
tcp: add more specific possible drop reasons in
tcp_rcv_synsent_state_process()
tcp: add dropreasons in tcp_rcv_state_process()
tcp: make the dropreason really work when calling
tcp_rcv_state_process()
tcp: make dropreason in tcp_child_process() work
tcp: get rid of NOT_SEPCIFIED reason in tcp_v4/6_do_rcv
include/net/dropreason-core.h | 22 +++++++++++++++++++++-
include/net/tcp.h | 4 ++--
net/ipv4/tcp_input.c | 28 +++++++++++++++++++---------
net/ipv4/tcp_ipv4.c | 20 ++++++++++++--------
net/ipv4/tcp_minisocks.c | 9 +++++----
net/ipv6/tcp_ipv6.c | 20 ++++++++++++--------
6 files changed, 71 insertions(+), 32 deletions(-)
--
2.37.3
next reply other threads:[~2024-02-12 9:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 9:28 Jason Xing [this message]
2024-02-12 9:28 ` [PATCH net-next v3 1/6] tcp: introduce another three dropreasons in receive path Jason Xing
2024-02-12 9:28 ` [PATCH net-next v3 2/6] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process() Jason Xing
2024-02-12 9:28 ` [PATCH net-next v3 3/6] tcp: add dropreasons in tcp_rcv_state_process() Jason Xing
2024-02-12 15:32 ` Eric Dumazet
2024-02-12 15:52 ` Jason Xing
2024-02-12 16:19 ` Eric Dumazet
2024-02-12 23:44 ` Jason Xing
2024-02-13 1:48 ` Jason Xing
2024-02-13 4:06 ` Kuniyuki Iwashima
2024-02-13 6:36 ` Jason Xing
2024-02-13 9:35 ` Eric Dumazet
2024-02-13 10:29 ` Jason Xing
2024-02-13 12:03 ` Eric Dumazet
2024-02-13 12:38 ` Jason Xing
2024-02-13 12:58 ` Jason Xing
2024-02-12 9:28 ` [PATCH net-next v3 4/6] tcp: make the dropreason really work when calling tcp_rcv_state_process() Jason Xing
2024-02-12 9:28 ` [PATCH net-next v3 5/6] tcp: make dropreason in tcp_child_process() work Jason Xing
2024-02-12 9:28 ` [PATCH net-next v3 6/6] tcp: get rid of NOT_SEPCIFIED reason in tcp_v4/6_do_rcv Jason Xing
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=20240212092827.75378-1-kerneljasonxing@gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernelxing@tencent.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 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).