[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20181219.114939.1427985047556314324.davem@davemloft.net>
Date: Wed, 19 Dec 2018 11:49:39 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: tuong.t.lien@...tech.com.au
Cc: jon.maloy@...csson.com, netdev@...r.kernel.org,
tipc-discussion@...ts.sourceforge.net
Subject: Re: [net-next 0/5] tipc: tracepoints and trace_events in TIPC
From: Tuong Lien <tuong.t.lien@...tech.com.au>
Date: Wed, 19 Dec 2018 09:17:55 +0700
> The patch series is the first step of introducing a tracing framework in
> TIPC, which will assist in collecting complete & plentiful data for post
> analysis, even in the case of a single failure occurrence e.g. when the
> failure is unreproducible.
>
> The tracing code in TIPC utilizes the powerful kernel tracepoints, trace
> events features along with particular dump functions to trace the TIPC
> object data and events (incl. bearer, link, socket, node, etc.).
>
> The tracing code should generate zero-load to TIPC when the trace events
> are not enabled.
Series applied, thank you.
Powered by blists - more mailing lists