Twitter | Pretraživanje | |
Thorsten 'the Linux kernel logger' Leemhuis(6/6)
"[…] The apparent cause of at least some of the 5.5 slowdowns after bisecting turned out to be […] it explains why the likes of Red Hat's upstream developers and others weren't affected and thus not quickly jumping on the problem […]"
Reply Retweet Označi sa "sviđa mi se" More
Thorsten 'the Linux kernel logger' Leemhuis(6/6) 30. pro
Odgovor korisniku/ci @kernellogger
BTW, kudos for bisecting this, here Michael and his very strong focus on benchmarks uncovered a real problem, that's why I'm sharing an article from his side.
Reply Retweet Označi sa "sviđa mi se"
Thorsten 'the Linux kernel logger' Leemhuis(6/6) 6. sij
Odgovor korisniku/ci @kernellogger
Out of curiosity: Does anyone know how (or where) the performance regression(¹) was reported to the responsible developers? I can't find anything :-/ (¹) fixed in mainline ( ) and 5.5-rc5 ( )
Reply Retweet Označi sa "sviđa mi se"