All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next 0/4] add MPTCP_MIB_CURRESTAB
Date: Tue, 28 Nov 2023 22:14:02 +0800	[thread overview]
Message-ID: <cover.1701180777.git.geliang.tang@suse.com> (raw)

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/460

Geliang Tang (4):
  mptcp: add mib counter dec helper
  mptcp: add a current established counter
  mptcp: add ftrace callback of tcp_set_state
  selftests: mptcp: join: check CURRESTAB counters

 net/mptcp/Makefile                            |  1 +
 net/mptcp/mib.c                               |  1 +
 net/mptcp/mib.h                               |  8 +++
 net/mptcp/trace.c                             | 68 +++++++++++++++++++
 .../testing/selftests/net/mptcp/mptcp_join.sh | 58 ++++++++++++++--
 5 files changed, 131 insertions(+), 5 deletions(-)
 create mode 100644 net/mptcp/trace.c

-- 
2.35.3


             reply	other threads:[~2023-11-28 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 14:14 Geliang Tang [this message]
2023-11-28 14:14 ` [PATCH mptcp-next 1/4] mptcp: add mib counter dec helper Geliang Tang
2023-11-28 14:14 ` [PATCH mptcp-next 2/4] mptcp: add a current established counter Geliang Tang
2023-11-28 14:14 ` [PATCH mptcp-next 3/4] mptcp: add ftrace callback of tcp_set_state Geliang Tang
2023-11-29  2:40   ` kernel test robot
2023-11-29  2:40   ` kernel test robot
2023-11-28 14:14 ` [PATCH mptcp-next 4/4] selftests: mptcp: join: check CURRESTAB counters Geliang Tang
2023-11-28 14:33   ` selftests: mptcp: join: check CURRESTAB counters: Tests Results MPTCP CI
2023-11-28 14:39   ` selftests: mptcp: join: check CURRESTAB counters: Build Failure MPTCP CI

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.1701180777.git.geliang.tang@suse.com \
    --to=geliang.tang@suse.com \
    --cc=mptcp@lists.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 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.