As We Prepare For 2022, Linux Still Doesn't Have Standardized Per-Client GPU Stats Reporting

[phoronix]

Phoronix: As We Prepare For 2022, Linux Still Doesn't Have Standardized Per-Client GPU Stats Reporting

One of the Intel patch series we have been waiting to see mainlined since all the way back in 2018 is around per-client GPU metrics reporting for being able to show various GPU engine activity on a per-process basis. Every once in a while the patches have been revived but have yet to reach mainline. They recently were revved once again, leaving us hope that in 2022 we might finally see this standardized per-client/process GPU statistics reporting land in the mainline kernel...

https://www.phoronix.com/scan.php?page=news_item&px=Linux-2022-Per-Client-GPU-Stats

[anarki2]

Linux vs standards, haha. Just look at systemd, how much hate it gets to this day. Freedom of choice! (tm)

[perpetually high]

AMD needs to seriously go on a hiring spree. What’s the excuse for why they haven’t?

[tildearrow]

I agree. I wish there was a standard way...
It's too bad that we still have to use debugfs for it.

[ezst036]

AMD needs to seriously go on a hiring spree. What’s the excuse for why they haven’t?

From the outside looking in, it appears that AMD is wrapping up as many optimizations as it can find into the open source driver stack so that it could get to a place of focusing its developer talent on only one Linux driver stack instead of two of them.

[agd5f]

AMD needs to seriously go on a hiring spree. What’s the excuse for why they haven’t?

We are hiring as fast as we can. It is, unfortunately, a pretty tight labor market at the moment. If you know anyone that wants to work for AMD, please tell them to contact us!

[birdie]

AMD needs to seriously go on a hiring spree. What’s the excuse for why they haven’t?

1. Money. ~3% of your userbase dabbles with games, while the other 97% really play games.
2. The ease of development and support: under Windows you have stable Win32 API and WDM which will work for many years to come, if not decades. You also have basically a single platform where all users run the same version of your drivers. Under Linux you have GTK/Qt/FLTK which break compatibility all the time, and don't get me started on the Linux kernel APIs, or a complete lack of them. And then users may run different kernels (read amdgpu drivers), different Mesa stacks, different display servers, different WMs. This adds a metric ton of things that need to be tested and taken into account.

Developing for Linux is a whole lot costlier than for Windows.

[skeevy420]

We are hiring as fast as we can. It is, unfortunately, a pretty tight labor market at the moment. If you know anyone that wants to work for AMD, please tell them to contact us!

It doesn't help that your position labeled "Spring 2022 Linux Kernel Engineer Co-Op/ Intern" has "Master's Degree preferred" under Academic Credentials.

Oh, and the "Staff Technical Writer" position potentially has dependency issues.

Under preferred experience is: At least 7 years of Software Technical Writing experience (an Electronics Engineering or Computer Science background is strongly desired, but not essential). However, under Academic Credentials is: A BA or BS Engineering degree is required.

So is the Engineering background and degree required or not essential?

[CommunityMember]

So is the Engineering background and degree required or not essential?

Position "requirements" have always been suggestive, and not absolute. If you really believe you can make a contribution, apply, and if your other accomplishments and positions are appropriate, you could get that interview (and the job).

[coder]

We are hiring as fast as we can. It is, unfortunately, a pretty tight labor market at the moment. If you know anyone that wants to work for AMD, please tell them to contact us!

Aren't the Linux GPU driver positions all in Markham, Ontario? Not that it's not a nice place, but many probably don't want to relocate.