public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 6/6] flow, tcp: Add logging helpers for connection related messages
Date: Thu, 23 Nov 2023 07:58:45 +0100	[thread overview]
Message-ID: <20231123075845.6dfd16fa@elisabeth> (raw)
In-Reply-To: <20231123023629.2024938-7-david@gibson.dropbear.id.au>

On Thu, 23 Nov 2023 13:36:29 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> Most of the messages logged by the TCP code (be they errors, debug or
> trace messages) are related to a specific connection / flow.  We're fairly
> consistent about prefixing these with the type of connection and the
> connection / flow index.  However there are a few places where we put the
> index later in the message or omit it entirely.  The template with the
> prefix is also a little bulky to carry around for every message,
> particularly for spliced connections.
> 
> To help keep this consistent, introduce some helpers to log messages
> linked to a specific flow.  It takes the flow as a parameter and adds a
> uniform prefix to each message.  This makes things slightly neater now, but
> more importantly will help keep formatting consistent as we add more things
> to the flow table.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  flow.c       | 21 ++++++++++++++
>  flow.h       | 14 +++++++++
>  tcp.c        | 81 ++++++++++++++++++++++++----------------------------
>  tcp_splice.c | 61 +++++++++++++++++----------------------
>  4 files changed, 99 insertions(+), 78 deletions(-)
> 
> diff --git a/flow.c b/flow.c
> index 0fff119..cb2cf62 100644
> --- a/flow.c
> +++ b/flow.c
> @@ -64,3 +64,24 @@ void flow_table_compact(struct ctx *c, union flow *hole)
>  
>  	memset(from, 0, sizeof(*from));
>  }
> +
> +/** flow_log_ - Log flow-related message
> + * @f:		flow the message is related to
> + * @pri:	Log priority
> + * @fmt:	Format string
> + * @...:	printf-arguments
> + *
> + * @fmt must include an initial "%s" to expand to the prefix we generate
> + * (typically added by the flow_log() macro).

I don't understand how it does that -- flow_log() seems to just pass
__VA_ARGS__ through?

> + */
> +void flow_log_(const struct flow_common *f, int pri, const char *fmt, ...)
> +{
> +	char msg[BUFSIZ];
> +	va_list args;
> +
> +	va_start(args, fmt);
> +	(void)vsnprintf(msg, sizeof(msg), fmt, args);
> +	va_end(args);
> +
> +	logmsg(pri, "Flow %u (%s): %s", flow_idx(f), FLOW_TYPE(f), msg);
> +}
> diff --git a/flow.h b/flow.h
> index 9f49195..b6da516 100644
> --- a/flow.h
> +++ b/flow.h
> @@ -43,4 +43,18 @@ union flow;
>  
>  void flow_table_compact(struct ctx *c, union flow *hole);
>  
> +void flow_log_(const struct flow_common *f, int pri, const char *fmt, ...)
> +	__attribute__((format(printf, 3, 4)));
> +
> +#define flow_log(f_, pri, ...)	flow_log_(&(f_)->f, (pri), __VA_ARGS__)
> +
> +#define flow_dbg(f, ...)	flow_log((f), LOG_DEBUG, __VA_ARGS__)
> +#define flow_err(f, ...)	flow_log((f), LOG_ERR, __VA_ARGS__)
> +
> +#define flow_trace(f, ...)						\
> +	do {								\
> +		if (log_trace)						\
> +			flow_dbg((f), __VA_ARGS__);			\
> +	} while (0)
> +
>  #endif /* FLOW_H */

-- 
Stefano


  reply	other threads:[~2023-11-23  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  2:36 [PATCH 0/6] Introduce unified flow table, first steps David Gibson
2023-11-23  2:36 ` [PATCH 1/6] test: Make handling of shell prompts with escapes a little more reliable David Gibson
2023-11-23  2:36 ` [PATCH 2/6] flow, tcp: Generalise connection types David Gibson
2023-11-23  2:36 ` [PATCH 3/6] flow, tcp: Move TCP connection table to unified flow table David Gibson
2023-11-23  2:36 ` [PATCH 4/6] flow, tcp: Consolidate flow pointer<->index helpers David Gibson
2023-11-23  2:36 ` [PATCH 5/6] flow: Make unified version of flow table compaction David Gibson
2023-11-23  2:36 ` [PATCH 6/6] flow, tcp: Add logging helpers for connection related messages David Gibson
2023-11-23  6:58   ` Stefano Brivio [this message]
2023-11-23 22:14     ` David Gibson
2023-11-23  4:46 ` [PATCH 0/6] Introduce unified flow table, first steps David Gibson

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=20231123075845.6dfd16fa@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).