From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH v4 0/5] libtraceevent: Optimize the print of tep fields
Date: Tue, 10 Aug 2021 15:26:54 +0300 [thread overview]
Message-ID: <20210810122659.145759-1-y.karadz@gmail.com> (raw)
Provide new capabilities for printing the content of the individual
fields of the event.
Changes in v4:
- Directly applying the modification in tep_print_field() suggested
by Steven.
- Optimizing the loop over the tokens in tep_print_fields().
Steven Rostedt (1):
libtraceevent: Have all field args point to the field they represent
Yordan Karadzhov (VMware) (4):
libtraceevent: Add dynamic_offset()
libtraceevent: Improve tep_print_field()
libtraceevent: Optimize tep_print_fields()
libtraceevent: Add tep_print_selected_fields()
src/event-parse.c | 288 +++++++++++++++++++++++++++++-----------------
src/event-parse.h | 3 +
2 files changed, 185 insertions(+), 106 deletions(-)
--
2.30.2
next reply other threads:[~2021-08-10 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 12:26 Yordan Karadzhov (VMware) [this message]
2021-08-10 12:26 ` [PATCH v4 1/5] libtraceevent: Add dynamic_offset() Yordan Karadzhov (VMware)
2021-08-10 12:26 ` [PATCH v4 2/5] libtraceevent: Have all field args point to the field they represent Yordan Karadzhov (VMware)
2021-08-10 12:26 ` [PATCH v4 3/5] libtraceevent: Improve tep_print_field() Yordan Karadzhov (VMware)
2021-08-10 12:26 ` [PATCH v4 4/5] libtraceevent: Optimize tep_print_fields() Yordan Karadzhov (VMware)
2021-08-10 12:26 ` [PATCH v4 5/5] libtraceevent: Add tep_print_selected_fields() Yordan Karadzhov (VMware)
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=20210810122659.145759-1-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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.