public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: Greg KH <gregkh@linuxfoundation.org>, Kay Sievers <kay@vrfy.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [RFC PATCH 0/3] printk: Use a non-printable ASCII SOH for KERN_<LEVEL>
Date: Thu, 24 May 2012 15:49:30 -0700	[thread overview]
Message-ID: <cover.1337899274.git.joe@perches.com> (raw)

printk uses "<.>" as a start of record indicator.
This can waste a bit of space and causes a bit of
contortion to get a printk emitted that happens to
starts with "<.>".

Use ASCII Start-of-Header (0x01) as the KERN_LEVEL
initiator and save ~10K in an x86 defconfig.

Joe Perches (3):
  printk: Use a non-printable ASCII KERN_<LEVEL> initiator
  treewide: Fix declaration and uses of old KERN_<LEVEL> style
  printk: Set KERN_CONT to ""

 arch/arm/lib/io-acorn.S              |    4 +++-
 arch/arm/vfp/vfphw.S                 |    8 +++++---
 arch/frv/kernel/kernel_thread.S      |    2 +-
 drivers/staging/wlags49_h2/hcf.c     |    8 ++++----
 drivers/staging/wlags49_h2/wl_main.c |    4 ++--
 fs/btrfs/super.c                     |    9 +++++----
 include/linux/printk.h               |   23 +++++++++++++----------
 kernel/printk.c                      |    6 +++---
 net/bridge/netfilter/ebt_log.c       |    2 +-
 sound/core/misc.c                    |    8 ++++----
 10 files changed, 41 insertions(+), 33 deletions(-)

-- 
1.7.8.111.gad25c.dirty


             reply	other threads:[~2012-05-24 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 22:49 Joe Perches [this message]
2012-05-24 22:49 ` [RFC PATCH 1/3] printk: Use a non-printable ASCII KERN_<LEVEL> initiator Joe Perches
2012-05-24 22:49 ` [RFC PATCH 2/3] treewide: Fix declaration and uses of old KERN_<LEVEL> style Joe Perches
2012-05-24 22:49 ` [RFC PATCH 3/3] printk: Set KERN_CONT to "" Joe Perches

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=cover.1337899274.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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