From: Philo Lu <lulie@linux.alibaba.com>
To: bpf@vger.kernel.org
Cc: edumazet@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, dsahern@kernel.org,
mykolal@fb.com, shuah@kernel.org, laoar.shao@gmail.com,
fred.cc@alibaba-inc.com, xuanzhuo@linux.alibaba.com
Subject: [PATCH bpf-next v1 0/2] bpf: add mrtt and srtt as ctx->args for BPF_SOCK_OPS_RTT_CB
Date: Fri, 26 Apr 2024 00:17:22 +0800 [thread overview]
Message-ID: <20240425161724.73707-1-lulie@linux.alibaba.com> (raw)
These provides more information about tcp RTT estimation. The selftest for
BPF_SOCK_OPS_RTT_CB is extended for the added args.
changelogs
-> v1:
- extend rtt selftest for added args (suggested by Stanislav)
Philo Lu (2):
bpf: add mrtt and srtt as BPF_SOCK_OPS_RTT_CB args
selftests/bpf: extend BPF_SOCK_OPS_RTT_CB test for srtt and mrtt_us
include/net/tcp.h | 4 ++--
include/uapi/linux/bpf.h | 2 ++
net/ipv4/tcp_input.c | 4 ++--
tools/include/uapi/linux/bpf.h | 2 ++
tools/testing/selftests/bpf/prog_tests/tcp_rtt.c | 14 ++++++++++++++
tools/testing/selftests/bpf/progs/tcp_rtt.c | 6 ++++++
6 files changed, 28 insertions(+), 4 deletions(-)
--
2.32.0.3.g01195cf9f
next reply other threads:[~2024-04-25 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 16:17 Philo Lu [this message]
2024-04-25 16:17 ` [PATCH bpf-next v1 1/2] bpf: add mrtt and srtt as BPF_SOCK_OPS_RTT_CB args Philo Lu
2024-04-25 16:17 ` [PATCH bpf-next v1 2/2] selftests/bpf: extend BPF_SOCK_OPS_RTT_CB test for srtt and mrtt_us Philo Lu
2024-04-25 22:10 ` [PATCH bpf-next v1 0/2] bpf: add mrtt and srtt as ctx->args for BPF_SOCK_OPS_RTT_CB 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=20240425161724.73707-1-lulie@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=fred.cc@alibaba-inc.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yonghong.song@linux.dev \
/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