Running Linux 5.15-rc1 Causing A New Slowdown... Here's A Look

[perpetually high]

Really impressed you went straight to the bisect

Just gotta raise a bug next time and it'll be a home run

Not sure what you mean? He took it straight to the chief. Linus. Isn't that the pinnacle of "raising a bug"? Asking seriously.

[agd5f]

The Linux Foundation should seriously consider funding you, I mean no one is doing what you do.

Lots of people do this every day. Not everyone has a website to announce their findings, but users and developers find issues, report, debug, and fix them every day.

[perpetually high]

Lots of people do this every day. Not everyone has a website to announce their findings, but users and developers find issues, report, debug, and fix them every day.

That's certainly not fair to everything Michael brings to the table. Sure, others are doing some. That's good. More should be doing some and more than they already are, maybe.

We can highlight one person without having to recognize every other person doing good work (you, Marek, Bas, Alyssa, Dave Airlee, trying to think of names that pop up often), but Michael is in a league of his own. Clearly.

[agd5f]

That's certainly not fair to everything Michael brings to the table. Sure, others are doing some. That's good. More should be doing some and more than they already are, maybe.

We can highlight one person without having to recognize every other person doing good work (you, Marek, Bas, Alyssa, Dave Airlee, trying to think of names that pop up often), but Michael is in a league of his own. Clearly.

I think it's fine to highlight the good work that Michael does, but a lot of the replies on the thread imply that none else is doing any and if it weren't for Michael, no one would catch any regressions in the kernel.

[perpetually high]

I think it's fine to highlight the good work that Michael does, but a lot of the replies on the thread imply that none else is doing any and if it weren't for Michael, no one would catch any regressions in the kernel.

I've been frequenting for about 4 years now, and I haven't seen many do what he does. And the Google searches will back it up. He catches a lot of these things *at the perfect* time (while it's still in -rc and before it rears its ugly head), or even sometimes after the fact if there's a clear regression in a new kernel after a patch. That amd temp patch was one thing, but there's been so many regressions he's caught. He's invaluable because he's the watchdog of the Linux kernel performance. Think about it, he mentioned it to Linus. That's boss. He deserves a direct line.

I'm just saying, not disagreeing with you, but also think Michael is underrated even after everyone's words in this thread. But that's just my personal opinion. And I know you feel similar, but spade a spade, I think Michael is the sole one doing *exactly* what he does.

[FireBurn]

Not sure what you mean? He took it straight to the chief. Linus. Isn't that the pinnacle of "raising a bug"? Asking seriously.

No it isn't, if every issue that someone found went straight to Linus, he wouldn't be able to get any work done

There's a clear process for reporting bugs

[perpetually high]

No it isn't, if every issue that someone found went straight to Linus, he wouldn't be able to get any work done

There's a clear process for reporting bugs

This has been an ongoing problem it seems with memcg. But you know what, it doesn't matter. I don't know about this particular issue to talk more about it, you guys probably do. It's separate from the point I'm trying to make.

I'm well aware there's process and order by the way, but you don't know what steps were taken for Michael to ultimately reach out to Linus. You assume it was a) find bug b) text message Linus at 3am "you're not going to believe this." So you don't know, I don't know, but Michael and Linus do. If you want to know, try and inquiring, is all I'm trying to say.

Another thing: I think you are forgetting Linux is the following: [email protected]:torvalds/linux.git

torvalds/linux.git

Head hauncho

*He* is the Benevolent Dictator. It's his project. What he says, goes. I might be wrong in that, but I've yet to see contrary evidence. So if I'm wrong, let me know. I don't want to be wrong again.

[perpetually high]

I'm just saying, Michael was just following Linus's law:

In software development, Linus's law is the assertion that "given enough eyeballs, all bugs are shallow".

The law was formulated by Eric S. Raymond in his essay and book The Cathedral and the Bazaar (1999), and was named in honor of Linus Torvalds.[1][2]

A more formal statement is: "Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone." Presenting the code to multiple developers with the purpose of reaching consensus about its acceptance is a simple form of software reviewing. Researchers and practitioners have repeatedly shown the effectiveness of reviewing processes in finding bugs and security issues.[3]

Doesn't sound like he broke any rules. Tell the authorities they don't need to come. All is okay. Linus is on top of it.

[F.Ultra]

I'm really wondering W.T.F. are those guys doing with the huge amounts of money they get from Google, Facebook, Microsoft and all other members ???
I don't see them working to improve the desktop adoption, governments open source adoption or open standards adoption like Vulkan.

Or funding Michael as a full time employee with all the benefits for his amazing work at finding all these regressions and saving millions for all these funding members that use Linux.

I'm really disgusted to see this bullshit corrupt foundation that does nothing !

It's very easy to lookup if you are really interested. Here are their 2020 report https://www.linuxfoundation.org/wp-c...ort_120520.pdf

[agd5f]

I've been frequenting for about 4 years now, and I haven't seen many do what he does. And the Google searches will back it up. He catches a lot of these things *at the perfect* time (while it's still in -rc and before it rears its ugly head), or even sometimes after the fact if there's a clear regression in a new kernel after a patch. That amd temp patch was one thing, but there's been so many regressions he's caught. He's invaluable because he's the watchdog of the Linux kernel performance. Think about it, he mentioned it to Linus. That's boss. He deserves a direct line.

I'm just saying, not disagreeing with you, but also think Michael is underrated even after everyone's words in this thread. But that's just my personal opinion. And I know you feel similar, but spade a spade, I think Michael is the sole one doing *exactly* what he does.

I'm not discounting Michael's work, but there are lot of people that find regressions (performance or otherwise) and report the issues to bugzilla or the relevant developer, or even Linus himself. The issues are debugged and fixed. There are probably tons of times there were performance regressions that Michael never noticed because they just happened to be found and fixed between times when he tested. Michael tends to get a lot of publicity because he writes about them on his website. You can find lots of examples on LKML or other venues.