ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Hannes Reinecke <hare@suse.com>
Cc: theodore.tso@gmail.com, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Late KS topics
Date: Mon, 26 Oct 2015 23:51:10 +0900 (KST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1510262348190.8998@pobox.suse.cz> (raw)
In-Reply-To: <562E37D7.9080105@suse.com>

On Mon, 26 Oct 2015, Hannes Reinecke wrote:

>   The talk/proposal should be used to come to a consensus about
>   restricting printk() to high-priority, small volume messages,
>   and implement a different call (like log_printk()) for the
>   low-priority, high-volume traffic.

The printk() troubles are not only about the "high volume" vs. "very 
important", but also about the context of the caller.

The optimistic comment above printk() says that it can be called from any 
context, but that's not true for quite some time already.
So if printk() is going to be redesigned to be more lightweight, this 
aspect definitely needs to be taken into consideration as well.

-- 
Jiri Kosina
SUSE Labs

  parent reply	other threads:[~2015-10-26 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 14:25 Hannes Reinecke
2015-10-26 14:49 ` David Woodhouse
2015-10-26 14:51 ` Jiri Kosina [this message]
2015-10-27 23:53   ` Sergey Senozhatsky
2015-10-26 16:14 ` Luck, Tony
2015-10-27  0:23   ` Hannes Reinecke
2015-10-27  0:12 ` Mark Brown
     [not found]   ` <20151027005950.GA26445@localhost>
2015-10-27  1:39     ` [Ksummit-discuss] Deferred probing Mark Brown

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=alpine.LNX.2.00.1510262348190.8998@pobox.suse.cz \
    --to=jikos@kernel.org \
    --cc=hare@suse.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=theodore.tso@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