From: Jakub Kicinski <kuba@kernel.org>
To: jackygam2001 <jacky_gam_2001@163.com>
Cc: dkirjanov@suse.de, edumazet@google.com, davem@davemloft.net,
pabeni@redhat.com, rostedt@goodmis.org, mingo@redhat.com,
yoshfuji@linux-ipv6.org, dsahern@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org, yhs@fb.com,
ping.gan@dell.com
Subject: Re: [PATCH v2 net-next] tcp: Add tracepoint for tcp_set_ca_state
Date: Thu, 31 Mar 2022 20:12:29 -0700 [thread overview]
Message-ID: <20220331201229.1cbd4f0b@kernel.org> (raw)
In-Reply-To: <20220331082149.15910-1-jacky_gam_2001@163.com>
On Thu, 31 Mar 2022 16:21:49 +0800 jackygam2001 wrote:
> From: Ping Gan <jacky_gam_2001@163.com>
>
> The congestion status of a tcp flow may be updated since there
> is congestion between tcp sender and receiver. It makes sense to
> add tracepoint for congestion status set function to summate cc
> status duration and evaluate the performance of network
> and congestion algorithm. The backgound of this patch is below.
>
> Link: https://github.com/iovisor/bcc/pull/3899
>
> Signed-off-by: Ping Gan <jacky_gam_2001@163.com>
# Form letter - net-next is closed
We have already sent the networking pull request for 5.18
and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after 5.18-rc1 is cut.
RFC patches sent for review only are obviously welcome at any time.
prev parent reply other threads:[~2022-04-01 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 13:01 [PATCH] tcp: Add tracepoint for tcp_set_ca_state jackygam2001
2022-03-30 13:33 ` Denis Kirjanov
2022-03-31 8:21 ` [PATCH v2 net-next] " jackygam2001
2022-04-01 3:12 ` Jakub Kicinski [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=20220331201229.1cbd4f0b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dkirjanov@suse.de \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jacky_gam_2001@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ping.gan@dell.com \
--cc=rostedt@goodmis.org \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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.