[lkml]   [2018]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Would you help to tell why async printk solution was not taken to upstream kernel ?
Cc-ing Steven

On (03/04/18 20:10), Qixuan.Wu wrote:
> Hi Sergey, petr, and Jan,
> I find you wrote a patch set of "[PATCH v12 0/3] printk: Make printk()
> completely async"(, and many people
> have reviewd. But I did not see them be taken to upstream kernel. Would
> you please help to tell me the reason ? Is it just only because of the
> LOG_CONT scenario (4th patch) ?


Thanks for your email, we desperately need more feedback from
people who are facing printk() related issues. While, certainly, I'm not
happy to hear that printk() causes troubles on your side.

Regarding the async printk patch set. It's still "work in
progress", and probably will take some time (due to various reasons,
LOG_CONT is not one of them).

> Anyway, now we also face the same problem, many CPU are printking at
> the same time, but the poor one takes the lock and printk to console for
> long time. Would you please help to tell does anybody are writing some
> solution and try to fix this ?

Yes. 4.16 has Steven's patch which tweaks printk() in a very smart
way and addresses some of the issues printk() has. If you can't test 4.16
(quite possible), then the commits you'd want to take a look at are
(Linus's tree):

dbdda842fe96f89 printk: Add console owner and waiter logic to load balance console writes
c162d5b4338d72d printk: Hide console waiter logic into helpers
fd5f7cde1b85d4c printk: Never set console_may_schedule in console_trylock()
c14376de3a1befa printk: Wake klogd when passing console_lock owner

If you can backport those, test and tell us about your experience - would be
great and very much appreciated.


 \ /
  Last update: 2018-03-04 14:02    [W:0.091 / U:10.548 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site