From: Petr Mladek <pmladek@suse.com>
To: Joe Perches <joe@perches.com>
Cc: Steven Rostedt <srostedt@redhat.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: printk discussions at KS
Date: Thu, 2 Nov 2017 13:45:47 +0100 [thread overview]
Message-ID: <20171102124547.GC31148@pathway.suse.cz> (raw)
In-Reply-To: <1509588743.31043.71.camel@perches.com>
On Wed 2017-11-01 19:12:23, Joe Perches wrote:
> As I was not there, and I know about as much as anyone
> about printk internals, can you please post a recap of
> what was discussed, technical and other, about printk
> improvements at the kernel-summit?
>
> If there was a pdf/powerpoint, that'd be nice to post too.
There is a nice summary of the discussion at
https://lwn.net/Articles/737822/
In short, it is the old problem with possible soft-lockups.
There were send many variants of a solution based on offloading
and kthreads. We discussed yet another solution proposed
by Steven.
Best Regards,
Petr
prev parent reply other threads:[~2017-11-02 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 2:12 printk discussions at KS Joe Perches
2017-11-02 12:45 ` Petr Mladek [this message]
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=20171102124547.GC31148@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=srostedt@redhat.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