From: Joe Perches <joe@perches.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Move printk_delay to separate file
Date: Fri, 07 Jul 2017 22:44:19 -0700 [thread overview]
Message-ID: <1499492659.20988.14.camel@perches.com> (raw)
In-Reply-To: <20170708052420.GC488@tigerII.localdomain>
On Sat, 2017-07-08 at 14:24 +0900, Sergey Senozhatsky wrote:
> On (07/07/17 11:08), Joe Perches wrote:
> > printk.c is a huge file with too many local functions for a
> > human to read and easily parse.
> >
> > Start to separate out bits into smaller files.
> >
> > Miscellanea:
> >
> > o Rename suppress_message_printing to printk_suppress_message
> > o Add function definitions to printk.h
>
> I don't mind, in general, but I'm a bit hesitant. we want to have
> automatic printk throttling (printk delay basically) and we need
> some of those printk-internal *_seq numbers to see how far consoles
> are behind the logbuf. so either we need to 'un-static' those *_seq
> and extern them in delay.c or simply keep printk-delay machinery in
> printk.c and add the new function.
>
> // p.s. I'll take a look at the patch a bit later. I'm on a sick leave now.
Hey Sergey.
Basically, this is a simple trial patch.
printk is getting nothing but more complex.
I believe printk is in real need of logical separation
into multiple parts to isolate the various logic bits.
o console
o kmsg/devkmsg
o logbuf
o syslog
etc...
next prev parent reply other threads:[~2017-07-08 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 18:08 Joe Perches
2017-07-08 5:24 ` Sergey Senozhatsky
2017-07-08 5:44 ` Joe Perches [this message]
2017-07-14 15:17 ` Petr Mladek
2017-07-14 15:45 ` Joe Perches
2017-07-14 15:57 ` Petr Mladek
2017-07-14 16:14 ` 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=1499492659.20988.14.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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
Powered by JetHome