Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-23 Thread Sergey Senozhatsky
On (03/23/17 11:40), Petr Mladek wrote: [..] > Let me do one more attempt for a generic name. What about? > > printk_console_press();or try_harder() or push() > printk_console_relax(); > > or something like this? I replied in another thread. how about printk_rescue? -ss

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-23 Thread Sergey Senozhatsky
On (03/23/17 11:40), Petr Mladek wrote: [..] > Let me do one more attempt for a generic name. What about? > > printk_console_press();or try_harder() or push() > printk_console_relax(); > > or something like this? I replied in another thread. how about printk_rescue? -ss

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-23 Thread Petr Mladek
On Thu 2017-03-23 14:12:42, Sergey Senozhatsky wrote: > On (03/22/17 17:40), Petr Mladek wrote: > [..] > > > +void console_printing_thread_off(void) > > > +{ > > > + printk_kthread_disable++; > > > + barrier(); > > > +} > > > + > > > +/* This re-enables printk_kthread offloading. */ > > > +void

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-23 Thread Petr Mladek
On Thu 2017-03-23 14:12:42, Sergey Senozhatsky wrote: > On (03/22/17 17:40), Petr Mladek wrote: > [..] > > > +void console_printing_thread_off(void) > > > +{ > > > + printk_kthread_disable++; > > > + barrier(); > > > +} > > > + > > > +/* This re-enables printk_kthread offloading. */ > > > +void

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-23 Thread Sergey Senozhatsky
On (03/22/17 17:40), Petr Mladek wrote: [..] > > +void console_printing_thread_off(void) > > +{ > > + printk_kthread_disable++; > > + barrier(); > > +} > > + > > +/* This re-enables printk_kthread offloading. */ > > +void console_printing_thread_on(void) > > +{ > > + barrier(); > > +

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-23 Thread Sergey Senozhatsky
On (03/22/17 17:40), Petr Mladek wrote: [..] > > +void console_printing_thread_off(void) > > +{ > > + printk_kthread_disable++; > > + barrier(); > > +} > > + > > +/* This re-enables printk_kthread offloading. */ > > +void console_printing_thread_on(void) > > +{ > > + barrier(); > > +

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-22 Thread Petr Mladek
On Mon 2017-03-06 21:45:51, Sergey Senozhatsky wrote: > This patch introduces a dedicated printing kernel thread - printk_kthread. > The main purpose of this kthread is to offload printing to a non-atomic > and always scheduleable context, which eliminates 4) and makes 1)-3) less > critical.

Re: [RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-22 Thread Petr Mladek
On Mon 2017-03-06 21:45:51, Sergey Senozhatsky wrote: > This patch introduces a dedicated printing kernel thread - printk_kthread. > The main purpose of this kthread is to offload printing to a non-atomic > and always scheduleable context, which eliminates 4) and makes 1)-3) less > critical.

[RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-06 Thread Sergey Senozhatsky
printk() is quite complex internally and, basically, it does two slightly independent things: a) adds a new message to a kernel log buffer (log_store()) b) prints kernel log messages to serial consoles (console_unlock()) while (a) is guaranteed to be executed by printk(), (b) is not, for a

[RFC][PATCH 1/4] printk: introduce printing kernel thread

2017-03-06 Thread Sergey Senozhatsky
printk() is quite complex internally and, basically, it does two slightly independent things: a) adds a new message to a kernel log buffer (log_store()) b) prints kernel log messages to serial consoles (console_unlock()) while (a) is guaranteed to be executed by printk(), (b) is not, for a