[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180305154524.2056b773@gandalf.local.home>
Date: Mon, 5 Mar 2018 15:45:24 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: "Qixuan.Wu" <qixuan.wu@...ux.alibaba.com>,
linux-kernel-owner <linux-kernel-owner@...r.kernel.org>,
Petr Mladek <pmladek@...e.com>, Jan Kara <jack@...e.cz>,
linux-kernel <linux-kernel@...r.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
"chenggang.qin" <chenggang.qin@...ux.alibaba.com>,
caijingxian <caijingxian@...ux.alibaba.com>,
"yuanliang.wyl" <yuanliang.wyl@...baba-inc.com>
Subject: Re: Would you help to tell why async printk solution was not taken
to upstream kernel ?
On Mon, 5 Mar 2018 11:14:16 +0900
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> wrote:
> It can print more than "one full buffer worth". In theory and on practice.
How so? As soon as another process adds to the buffer, it will take
over the printing.
-- Steve
Powered by blists - more mailing lists