From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
dsahern@kernel.org, kuniyu@amazon.com, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next v4 0/6] introduce dropreasons in tcp receive path
Date: Tue, 13 Feb 2024 18:23:38 -0800 [thread overview]
Message-ID: <20240213182338.397f6d29@kernel.org> (raw)
In-Reply-To: <20240213140508.10878-1-kerneljasonxing@gmail.com>
On Tue, 13 Feb 2024 22:05:02 +0800 Jason Xing wrote:
> As title 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.
Please do not post two similar sets at the same time.
next prev parent reply other threads:[~2024-02-14 2:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:05 [PATCH net-next v4 0/6] introduce dropreasons in tcp receive path Jason Xing
2024-02-13 14:05 ` [PATCH net-next v4 1/6] tcp: introduce another three dropreasons in " Jason Xing
2024-02-13 15:49 ` David Ahern
2024-02-13 17:00 ` Jason Xing
2024-02-13 14:05 ` [PATCH net-next v4 2/6] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process() Jason Xing
2024-02-13 14:05 ` [PATCH net-next v4 3/6] tcp: add dropreasons in tcp_rcv_state_process() Jason Xing
2024-02-13 14:05 ` [PATCH net-next v4 4/6] tcp: make the dropreason really work when calling tcp_rcv_state_process() Jason Xing
2024-02-13 14:05 ` [PATCH net-next v4 5/6] tcp: make dropreason in tcp_child_process() work Jason Xing
2024-02-13 14:05 ` [PATCH net-next v4 6/6] tcp: get rid of NOT_SEPCIFIED reason in tcp_v4/6_do_rcv Jason Xing
2024-02-14 2:23 ` Jakub Kicinski [this message]
2024-02-14 12:38 ` [PATCH net-next v4 0/6] introduce dropreasons in tcp receive path 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=20240213182338.397f6d29@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuniyu@amazon.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 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.