linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@kernel.org, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	linux-mm@kvack.org, xiyou.wangcong@gmail.com,
	dave.hansen@intel.com, hannes@cmpxchg.org, mgorman@suse.de,
	pmladek@suse.com, sergey.senozhatsky@gmail.com, vbabka@suse.cz,
	peterz@infradead.org, torvalds@linux-foundation.org,
	jack@suse.cz, mathieu.desnoyers@efficios.com,
	rostedt@rostedt.homelinux.com
Subject: Re: [PATCH v4] printk: Add console owner and waiter logic to loadbalance console writes
Date: Thu, 9 Nov 2017 19:22:58 +0900	[thread overview]
Message-ID: <201711091922.IHJ81787.OVQFFJOSOLtHMF@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20171109101138.qmy3366myzjafexr@dhcp22.suse.cz>

Michal Hocko wrote:
> Hi,
> assuming that this passes warn stall torturing by Tetsuo, do you think
> we can drop http://lkml.kernel.org/r/1509017339-4802-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp
> from the mmotm tree?

I don't think so.

The rule that "do not try to printk() faster than the kernel can write to
consoles" will remain no matter how printk() changes. Unless asynchronous
approach like https://lwn.net/Articles/723447/ is used, I think we can't
obtain useful information.

  reply	other threads:[~2017-11-09 10:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 15:27 [PATCH v4] printk: Add console owner and waiter logic to load balance console writes Steven Rostedt
2017-11-09 10:12 ` Michal Hocko
2017-11-09 10:22   ` Tetsuo Handa [this message]
2017-11-09 10:26     ` [PATCH v4] printk: Add console owner and waiter logic to loadbalance " Michal Hocko
2017-11-09 11:03       ` Tetsuo Handa
2017-11-09 11:31         ` Michal Hocko
2017-11-09 12:07           ` Tetsuo Handa
2017-11-24 15:54 ` [PATCH v4] printk: Add console owner and waiter logic to load balance " Petr Mladek
2017-11-24 15:58   ` Petr Mladek
2017-11-27  8:53     ` Byungchul Park
2017-11-28  1:42     ` Byungchul Park
2017-12-08 14:00       ` Petr Mladek
2017-12-12  5:39         ` Sergey Senozhatsky
2017-12-12 19:27           ` Steven Rostedt
2017-12-13  1:50             ` Sergey Senozhatsky
2017-12-14 14:34             ` Petr Mladek
2017-12-14 13:51     ` Petr Mladek
2017-11-27  8:48 ` Byungchul Park
2017-11-28  6:23   ` Sergey Senozhatsky
2017-12-22 10:31 ` Petr Mladek
2017-12-22 12:44   ` Steven Rostedt
2018-01-10 12:50     ` Petr Mladek

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=201711091922.IHJ81787.OVQFFJOSOLtHMF@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=rostedt@rostedt.homelinux.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=xiyou.wangcong@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).