lkml.org 
[lkml]   [2017]   [Dec]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v4] printk: Add console owner and waiter logic to load balance console writes
On Fri, 22 Dec 2017 11:31:31 +0100
Petr Mladek <pmladek@suse.com> wrote:

> > Index: linux-trace.git/kernel/printk/printk.c
> > ===================================================================
> > --- linux-trace.git.orig/kernel/printk/printk.c
> > +++ linux-trace.git/kernel/printk/printk.c
> > @@ -2141,6 +2196,7 @@ void console_unlock(void)
> > static u64 seen_seq;
> > unsigned long flags;
> > bool wake_klogd = false;
> > + bool waiter = false;
> > bool do_cond_resched, retry;
> >
> > if (console_suspended) {
> > @@ -2229,14 +2285,64 @@ skip:
> > console_seq++;
> > raw_spin_unlock(&logbuf_lock);
> >
> > + /*
> > + * While actively printing out messages, if another printk()
> > + * were to occur on another CPU, it may wait for this one to
> > + * finish. This task can not be preempted if there is a
> > + * waiter waiting to take over.
> > + */
> > + raw_spin_lock(&console_owner_lock);
> > + console_owner = current;
> > + raw_spin_unlock(&console_owner_lock);
>
> One idea. We could do the above only when "do_cond_resched" is false.
> I mean that we could allow stealing the console duty only from
> atomic context.

I'd like to hold off before making a change like that. I thought about
it, but by saying "atomic" is more important than "non-atomic" can also
lead to problems. Once you don't allow stealing, you just changed
printk to be unbounded again. Maybe that's not an issue. But I'd rather
add that as an enhancement in case. I could make this a patch series,
and we can build cases like this up.

>
> If I get it correctly, this variable is always true in schedulable
> context.
>
> > +
> > + /* The waiter may spin on us after setting console_owner */
> > + spin_acquire(&console_owner_dep_map, 0, 0, _THIS_IP_);
> > +
> > stop_critical_timings(); /* don't trace print latency */
> > call_console_drivers(ext_text, ext_len, text, len);
> > start_critical_timings();
> > +
> > + raw_spin_lock(&console_owner_lock);
> > + waiter = READ_ONCE(console_waiter);
> > + console_owner = NULL;
> > + raw_spin_unlock(&console_owner_lock);
> > +
> > + /*
> > + * If there is a waiter waiting for us, then pass the
> > + * rest of the work load over to that waiter.
> > + */
> > + if (waiter)
> > + break;
> > +
> > + /* There was no waiter, and nothing will spin on us here */
> > + spin_release(&console_owner_dep_map, 1, _THIS_IP_);
> > +
> > printk_safe_exit_irqrestore(flags);
> >
> > if (do_cond_resched)
> > cond_resched();
>
> On the contrary, we could allow steeling the console semaphore
> when sleeping here. It would allow to get the messages out
> faster. It might help to move the duty to someone who is
> actually producing many messages or even the panic() caller.

Good point. I'll add a patch that adds that feature too.

Thanks!

-- Steve

\
 
 \ /
  Last update: 2017-12-22 13:45    [W:0.157 / U:1.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site