All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yixin Shen <bobankhshen@gmail.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@kernel.org, song@kernel.org, yhs@fb.com,
	bobankhshen@gmail.com
Subject: [PATCH bpf-next v2 0/2] Allow BPF TCP CCs to write app_limited
Date: Wed, 29 Mar 2023 07:35:56 +0000	[thread overview]
Message-ID: <20230329073558.8136-1-bobankhshen@gmail.com> (raw)

This series allow BPF TCP CCs to write app_limited of struct
tcp_sock. A built-in CC or one from a kernel module is already
able to write to app_limited of struct tcp_sock. Until now,
a BPF CC doesn't have write access to this member of struct
tcp_sock.

v2:
 - Merge the test of writing app_limited into the test of
   writing sk_pacing. (Martin KaFai Lau)
 
Yixin Shen (2):
  bpf: allow a TCP CC to write app_limited
  selftests/bpf: test a BPF CC writing app_limited

 net/ipv4/bpf_tcp_ca.c                               |  3 +++
 .../selftests/bpf/progs/tcp_ca_write_sk_pacing.c    | 13 ++++++++++++-
 2 files changed, 15 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2023-03-29  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  7:35 Yixin Shen [this message]
2023-03-29  7:35 ` [PATCH bpf-next v2 1/2] bpf: allow a TCP CC to write app_limited Yixin Shen
2023-03-29  7:35 ` [PATCH bpf-next v2 2/2] selftests/bpf: test a BPF CC writing app_limited Yixin Shen
2023-03-29 20:40 ` [PATCH bpf-next v2 0/2] Allow BPF TCP CCs to write app_limited 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=20230329073558.8136-1-bobankhshen@gmail.com \
    --to=bobankhshen@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --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 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.