From: Paolo Abeni <pabeni@redhat.com>
To: Geliang Tang <geliangtang@gmail.com>,
mptcp@lists.01.org, mptcp@lists.linux.dev
Subject: Re: [MPTCP][PATCH v2 mptcp-next 2/5] mptcp: add tracepoint in mptcp_subflow_get_send
Date: Mon, 29 Mar 2021 15:52:10 +0200 [thread overview]
Message-ID: <3bd1de25c30c16a76cdb2883b68fc1991002235a.camel@redhat.com> (raw)
In-Reply-To: <ffa353e9982d4795058abc87f1e2f52bc29e430b.1616575602.git.geliangtang@gmail.com>
On Wed, 2021-03-24 at 16:51 +0800, Geliang Tang wrote:
> This patch added a tracepoint in the packet scheduler function
> mptcp_subflow_get_send().
>
> Suggested-by: Paolo Abeni <pabeni@redhat.com>
> Signed-off-by: Geliang Tang <geliangtang@gmail.com>
> ---
> include/trace/events/mptcp.h | 43 ++++++++++++++++++++++++++++++++++++
> net/mptcp/protocol.c | 4 ++++
> 2 files changed, 47 insertions(+)
> create mode 100644 include/trace/events/mptcp.h
>
> diff --git a/include/trace/events/mptcp.h b/include/trace/events/mptcp.h
> new file mode 100644
> index 000000000000..06908ea6afb4
> --- /dev/null
> +++ b/include/trace/events/mptcp.h
> @@ -0,0 +1,43 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#undef TRACE_SYSTEM
> +#define TRACE_SYSTEM mptcp
> +
> +#if !defined(_TRACE_MPTCP_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _TRACE_MPTCP_H
> +
> +#include <linux/tracepoint.h>
> +
> +TRACE_EVENT(mptcp_subflow_get_send,
> +
> + TP_PROTO(struct mptcp_subflow_context *subflow, struct sock *ssk),
> +
> + TP_ARGS(subflow, ssk),
> +
> + TP_STRUCT__entry(
> + __field(bool, active)
> + __field(bool, free)
> + __field(u32, snd_wnd)
> + __field(u32, pace)
> + __field(u8, backup)
> + __field(u64, ratio)
> + ),
> +
> + TP_fast_assign(
> + __entry->active = mptcp_subflow_active(subflow);
> + __entry->free = sk_stream_memory_free(subflow->tcp_sock);
I'm sorry for not noticing the thing before, but subflow->tcp_sock can
be potentially a TIME_WAIT socket. We need to do:
sk = sk_fullsock(subflow->tcp_sock);
and checking for sk being != NULL before accessing any tcp_sock or sock
fields.
Note that the caller don't need such thing explicitly, because it
accesses such fields only for mptcp_subflow_active() sockets - which
are NOT TIME_WAIT ones.
> + __entry->snd_wnd = tcp_sk(ssk)->snd_wnd;
> + __entry->pace = ssk->sk_pacing_rate;
> + __entry->backup = subflow->backup;
> + __entry->ratio = div_u64((u64)ssk->sk_wmem_queued << 32, __entry->pace);
Here we need to check for !__entry->pace, to avoid possible division by
0.
Thanks!
Paolo
next prev parent reply other threads:[~2021-03-29 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 8:51 [MPTCP][PATCH v2 mptcp-next 0/5] add tracepoints Geliang Tang
2021-03-24 8:51 ` [MPTCP][PATCH v2 mptcp-next 1/5] mptcp: export mptcp_subflow_active Geliang Tang
2021-03-24 8:51 ` [MPTCP][PATCH v2 mptcp-next 2/5] mptcp: add tracepoint in mptcp_subflow_get_send Geliang Tang
2021-03-24 8:51 ` [MPTCP][PATCH v2 mptcp-next 3/5] mptcp: add tracepoint in get_mapping_status Geliang Tang
2021-03-24 8:51 ` [MPTCP][PATCH v2 mptcp-next 4/5] mptcp: add tracepoint in ack_update_msk Geliang Tang
2021-03-24 8:51 ` [MPTCP][PATCH v2 mptcp-next 5/5] mptcp: add tracepoint in subflow_check_data_avail Geliang Tang
2021-03-29 14:03 ` [MPTCP][PATCH v2 mptcp-next 4/5] mptcp: add tracepoint in ack_update_msk Paolo Abeni
2021-03-29 14:00 ` [MPTCP][PATCH v2 mptcp-next 3/5] mptcp: add tracepoint in get_mapping_status Paolo Abeni
2021-03-29 13:52 ` Paolo Abeni [this message]
2021-03-29 13:52 ` [MPTCP] [MPTCP][PATCH v2 mptcp-next 1/5] mptcp: export mptcp_subflow_active 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=3bd1de25c30c16a76cdb2883b68fc1991002235a.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=geliangtang@gmail.com \
--cc=mptcp@lists.01.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox