mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: [PATCH v2 0/3] trace: Use simpler seq_file functions
Date: Sat,  8 Nov 2014 21:42:09 +0100	[thread overview]
Message-ID: <1415479332-25944-1-git-send-email-linux@rasmusvillemoes.dk> (raw)
In-Reply-To: <1410513954-28909-5-git-send-email-linux@rasmusvillemoes.dk>

Using printf to print a simple string or puts to print a single
character is more expensive than it needs to be. Also, consecutive
puts calls can be replaced by a single call. These patches do this to
kernel/trace/, saving ~256 bytes of .text.

v2: Keep the original splitting of strings across lines.

Rasmus Villemoes (3):
  trace: Replace seq_printf by simpler equivalents
  trace: Merge consecutive seq_puts calls
  trace: Replace single-character seq_puts with seq_putc

 kernel/trace/ftrace.c                | 30 +++++++-------
 kernel/trace/trace.c                 | 78 ++++++++++++++++++------------------
 kernel/trace/trace_branch.c          | 32 +++++++--------
 kernel/trace/trace_events.c          |  4 +-
 kernel/trace/trace_events_trigger.c  |  6 +--
 kernel/trace/trace_functions.c       |  2 +-
 kernel/trace/trace_functions_graph.c | 28 ++++++-------
 kernel/trace/trace_kprobe.c          | 12 +++---
 kernel/trace/trace_printk.c          |  2 +-
 kernel/trace/trace_uprobe.c          |  4 +-
 10 files changed, 99 insertions(+), 99 deletions(-)

-- 
2.0.4


  parent reply	other threads:[~2014-11-08 20:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  9:25 [PATCH 0/6] Small seqfile-use improvements Rasmus Villemoes
2014-09-12  9:25 ` [PATCH 1/6] Coccinelle: Semantic patch for replacing puts with putc Rasmus Villemoes
2014-09-12 11:08   ` SF Markus Elfring
2014-09-12  9:25 ` [PATCH 2/6] Coccinelle: Semantic patch for joining seq_puts calls Rasmus Villemoes
2014-09-12  9:25 ` [PATCH 3/6] Coccinelle: Semantic patch for replacing seq_printf calls with equivalent but simpler functions Rasmus Villemoes
2014-09-12  9:25 ` [PATCH 4/6] trace: Replace seq_printf by simpler equivalents Rasmus Villemoes
2014-11-05 22:34   ` Steven Rostedt
2014-11-05 22:44     ` Rasmus Villemoes
2014-11-06  0:34       ` Steven Rostedt
2014-11-05 22:51     ` Joe Perches
2014-11-06  0:38       ` Steven Rostedt
2014-11-06  0:47         ` Joe Perches
2014-11-08 20:42   ` Rasmus Villemoes [this message]
2014-11-08 20:42     ` [PATCH v2 1/3] " Rasmus Villemoes
2014-11-14  2:31       ` Steven Rostedt
2014-11-08 20:42     ` [PATCH v2 2/3] trace: Merge consecutive seq_puts calls Rasmus Villemoes
2014-11-08 20:42     ` [PATCH v2 3/3] trace: Replace single-character seq_puts with seq_putc Rasmus Villemoes
2014-11-14  2:34       ` Steven Rostedt
2014-09-12  9:25 ` [PATCH 5/6] trace: Merge consecutive seq_puts calls Rasmus Villemoes
2014-09-12  9:25 ` [PATCH 6/6] trace: Replace single-character seq_puts with seq_putc Rasmus Villemoes

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=1415479332-25944-1-git-send-email-linux@rasmusvillemoes.dk \
    --to=linux@rasmusvillemoes.dk \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®