MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v2 0/3] Fixes for "use bpf_iter in bpf schedulers" v8
Date: Thu, 24 Oct 2024 18:22:01 +0800	[thread overview]
Message-ID: <cover.1729765157.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v2:
 - Use mptcp_stream_memory_free instead of using tcp_stream_memory_free.

Fix mptcp_join.sh (22) and packetdrill errors in "use bpf_iter in bpf
schedulers" (v8) reported by CI.

Depends on:
 - "use bpf_iter in bpf schedulers" v8

Based-on: <cover.1729676320.git.tanggeliang@kylinos.cn>

Geliang Tang (3):
  Squash to "mptcp: check sk_stream_memory_free in loop"
  Squash to "bpf: Export mptcp packet scheduler helpers"
  Squash to "selftests/bpf: Add bpf_burst scheduler & test"

 net/mptcp/bpf.c                                     | 7 ++++++-
 net/mptcp/protocol.c                                | 5 +++--
 tools/testing/selftests/bpf/progs/mptcp_bpf_burst.c | 9 +++++----
 3 files changed, 14 insertions(+), 7 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-10-24 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 10:22 Geliang Tang [this message]
2024-10-24 10:22 ` [PATCH mptcp-next v2 1/3] Squash to "mptcp: check sk_stream_memory_free in loop" Geliang Tang
2024-10-24 10:22 ` [PATCH mptcp-next v2 2/3] Squash to "bpf: Export mptcp packet scheduler helpers" Geliang Tang
2024-10-24 10:22 ` [PATCH mptcp-next v2 3/3] Squash to "selftests/bpf: Add bpf_burst scheduler & test" Geliang Tang
2024-10-24 10:53 ` [PATCH mptcp-next v2 0/3] Fixes for "use bpf_iter in bpf schedulers" v8 MPTCP CI
2024-10-25  8:34 ` Geliang Tang

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=cover.1729765157.git.tanggeliang@kylinos.cn \
    --to=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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