From: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Uladzislau Rezki <urezki@gmail.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
RCU <rcu@vger.kernel.org>,
"quic_neeraju@quicinc.com" <quic_neeraju@quicinc.com>,
Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: RE: [PATCH 1/1] Reduce synchronize_rcu() waiting time
Date: Tue, 28 Mar 2023 01:28:01 +0000 [thread overview]
Message-ID: <SJ1PR11MB61792EA18F7F2BFD1E70916489889@SJ1PR11MB6179.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230327175059.1e8584cc@gandalf.local.home>
> From: Steven Rostedt <rostedt@goodmis.org>
> Sent: Tuesday, March 28, 2023 5:51 AM
> [...]
> Subject: Re: [PATCH 1/1] Reduce synchronize_rcu() waiting time
>
> On Mon, 27 Mar 2023 17:48:44 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > struct my_info {
> > /* store state info here */
> > };
> >
> > int main(...) {
> > struct tracecmd_input *handle;
> > struct my_info info;
> > char *file = argv[1];
> >
> > handle = tracecmd_open(file);
> >
> > tracecmd_follow_event(handle, "rcu", "rcu_batch_start",
> > batch_start, &info);
> >
> > tracecmd_follow_event(handle, "rcu", "rcu_batch_end",
> > batch_end, &info);
> >
> > tracecmd_follow_event(handle, "rcu", "rcu_invoke_callback",
> > invoke_callback, &info);
> >
> > tracecmd_iterate_events(handle, NULL, 0, NULL, NULL);
> >
> > tracecmd_close(handle);
> > }
>
> BTW, none of this code was actually tested, so I may have some syntax
> errors. I just did this straight from memory, as it's so easy ;-)
Thank you Steven for sharing the libtracecmd-based and libtraceevent-based
methods for trace parsing. Good to know this. This should simplify the code
to parse trace logs. Pretty useful for me/us ;-)
- Qiuxu
>
> -- Steve
prev parent reply other threads:[~2023-03-28 1:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 10:27 [PATCH 1/1] Reduce synchronize_rcu() waiting time Uladzislau Rezki (Sony)
2023-03-21 14:03 ` Zhuo, Qiuxu
2023-03-21 15:15 ` Uladzislau Rezki
2023-03-22 1:49 ` Zhuo, Qiuxu
2023-03-22 6:50 ` Uladzislau Rezki
2023-03-22 11:21 ` Zhuo, Qiuxu
2023-03-27 11:21 ` Zhang, Qiang1
2023-03-27 17:47 ` Uladzislau Rezki
2023-03-28 0:14 ` Zhang, Qiang1
2023-03-27 21:23 ` Joel Fernandes
2023-03-28 0:12 ` Zhang, Qiang1
2023-03-28 1:06 ` Paul E. McKenney
2023-03-28 1:32 ` Zhang, Qiang1
2023-03-28 1:59 ` Paul E. McKenney
2023-03-28 2:29 ` Joel Fernandes
2023-03-28 15:26 ` Paul E. McKenney
2023-03-28 22:14 ` Paul E. McKenney
2023-03-30 15:11 ` Joel Fernandes
2023-03-30 19:01 ` Paul E. McKenney
2023-03-30 15:09 ` Joel Fernandes
2023-03-30 15:43 ` Uladzislau Rezki
2023-03-30 18:58 ` Paul E. McKenney
2023-03-30 19:18 ` Uladzislau Rezki
2023-03-30 21:16 ` Paul E. McKenney
2023-03-31 10:55 ` Uladzislau Rezki
2023-03-31 18:39 ` Paul E. McKenney
2023-03-30 18:57 ` Paul E. McKenney
2023-03-27 21:48 ` Steven Rostedt
2023-03-27 21:50 ` Steven Rostedt
2023-03-28 1:28 ` Zhuo, Qiuxu [this message]
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=SJ1PR11MB61792EA18F7F2BFD1E70916489889@SJ1PR11MB6179.namprd11.prod.outlook.com \
--to=qiuxu.zhuo@intel.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).