Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

Sergey Senozhatsky
2018-01-11T05:10:46Z

On (01/10/18 17:29), Petr Mladek wrote:
[..]
> The next versions used lazy offload from console_unlock() when
> the thread spent there too much time. IMHO, this is one
> very promising solution. It guarantees that softlockup
> would never happen. But it tries hard to get the messages
> out immediately.

a small addition. my motivation was not exactly the "lazy offload",
but to keep the existing printk behavior as long as possible. and
that "as long as possible" is determined by watchdog threshold, which
is the only limit we must care about. as long as printing task spends
more than 1/2 of watchdog threshold - we offload. otherwise we don't
mess up with the existing logic/guarantees/etc.

there is also a bunch of other things in the patch now. but nothing
fantastically complex.

-ss