From: Martin KaFai Lau <martin.lau@linux.dev>
To: Yixin Shen <bobankhshen@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@kernel.org, song@kernel.org, yhs@fb.com,
bpf@vger.kernel.org
Subject: Re: [PATCH 2/2] selftests/bpf: test a BPF CC writing app_limited
Date: Tue, 28 Mar 2023 11:31:24 -0700 [thread overview]
Message-ID: <1dab862d-7070-2529-ba88-22cf73b2126a@linux.dev> (raw)
In-Reply-To: <20230328132035.50839-3-bobankhshen@gmail.com>
On 3/28/23 6:20 AM, Yixin Shen wrote:
> diff --git a/tools/testing/selftests/bpf/progs/tcp_ca_write_app_limited.c b/tools/testing/selftests/bpf/progs/tcp_ca_write_app_limited.c
> new file mode 100644
> index 000000000000..de5c9b5045a1
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/tcp_ca_write_app_limited.c
> @@ -0,0 +1,71 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include "vmlinux.h"
> +
> +#include <bpf/bpf_helpers.h>
> +#include <bpf/bpf_tracing.h>
> +
> +char _license[] SEC("license") = "GPL";
> +
> +#define USEC_PER_SEC 1000000UL
> +
> +#define min(a, b) ((a) < (b) ? (a) : (b))
> +
> +static inline struct tcp_sock *tcp_sk(const struct sock *sk)
> +{
> + return (struct tcp_sock *)sk;
> +}
> +
> +static inline unsigned int tcp_left_out(const struct tcp_sock *tp)
> +{
> + return tp->sacked_out + tp->lost_out;
> +}
> +
> +static inline unsigned int tcp_packets_in_flight(const struct tcp_sock *tp)
> +{
> + return tp->packets_out - tcp_left_out(tp) + tp->retrans_out;
> +}
> +
> +SEC("struct_ops/write_app_limited_init")
> +void BPF_PROG(write_app_limited_init, struct sock *sk)
> +{
> +#ifdef ENABLE_ATOMICS_TESTS
> + __sync_bool_compare_and_swap(&sk->sk_pacing_status, SK_PACING_NONE,
> + SK_PACING_NEEDED);
> +#else
> + sk->sk_pacing_status = SK_PACING_NEEDED;
> +#endif
> +}
> +
> +SEC("struct_ops/write_app_limited_cong_control")
> +void BPF_PROG(write_app_limited_cong_control, struct sock *sk,
> + const struct rate_sample *rs)
> +{
> + struct tcp_sock *tp = tcp_sk(sk);
> + unsigned long rate =
> + ((tp->snd_cwnd * tp->mss_cache * USEC_PER_SEC) << 3) /
> + (tp->srtt_us ?: 1U << 3);
> + sk->sk_pacing_rate = min(rate, sk->sk_max_pacing_rate);
> + tp->app_limited = (tp->delivered + tcp_packets_in_flight(tp)) ?: 1;
Please add this line testing tp->app_limited to tcp_ca_write_sk_pacing.c instead
of creating a new bpf prog that looks pretty much the same.
Also tag the subject with bpf-next in v2.
Others lgtm.
prev parent reply other threads:[~2023-03-28 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 13:20 [PATCH 0/2] Allow BPF TCP CCs to write app_limited Yixin Shen
2023-03-28 13:20 ` [PATCH 1/2] bpf: allow a TCP CC " Yixin Shen
2023-03-28 13:20 ` [PATCH 2/2] selftests/bpf: test a BPF CC writing app_limited Yixin Shen
2023-03-28 18:31 ` Martin KaFai Lau [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=1dab862d-7070-2529-ba88-22cf73b2126a@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bobankhshen@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.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