From: Geliang Tang <geliangtang@gmail.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliangtang@gmail.com>
Subject: [MPTCP][PATCH v3 mptcp-next 0/4] add tracepoints
Date: Tue, 30 Mar 2021 17:16:42 +0800 [thread overview]
Message-ID: <cover.1617095554.git.geliangtang@gmail.com> (raw)
v3:
- update the patch set as Paolo suggested.
- drop the patch "mptcp: export mptcp_subflow_active".
v2:
- add two new patches.
This patchset addressed issues 131, replace some/most pr_debug with trace
events. As Paolo suggested, we should add the tracepoints at "the packet
scheduler and the mapping status" first.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/131
Geliang Tang (4):
mptcp: add tracepoint in mptcp_subflow_get_send
mptcp: add tracepoint in get_mapping_status
mptcp: add tracepoint in ack_update_msk
mptcp: add tracepoint in subflow_check_data_avail
include/trace/events/mptcp.h | 158 +++++++++++++++++++++++++++++++++++
net/mptcp/options.c | 6 ++
net/mptcp/protocol.c | 7 ++
net/mptcp/subflow.c | 10 +--
4 files changed, 175 insertions(+), 6 deletions(-)
create mode 100644 include/trace/events/mptcp.h
--
2.30.2
next reply other threads:[~2021-03-30 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 9:16 Geliang Tang [this message]
2021-03-30 9:16 ` [MPTCP][PATCH v3 mptcp-next 1/4] mptcp: add tracepoint in mptcp_subflow_get_send Geliang Tang
2021-03-30 9:16 ` [MPTCP][PATCH v3 mptcp-next 2/4] mptcp: add tracepoint in get_mapping_status Geliang Tang
2021-03-30 9:16 ` [MPTCP][PATCH v3 mptcp-next 3/4] mptcp: add tracepoint in ack_update_msk Geliang Tang
2021-03-30 9:16 ` [MPTCP][PATCH v3 mptcp-next 4/4] mptcp: add tracepoint in subflow_check_data_avail Geliang Tang
2021-03-30 13:51 ` [MPTCP][PATCH v3 mptcp-next 1/4] mptcp: add tracepoint in mptcp_subflow_get_send Paolo Abeni
2021-03-30 17:26 ` Paolo Abeni
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.1617095554.git.geliangtang@gmail.com \
--to=geliangtang@gmail.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.