AMDGPU's Scheduler Might Get Picked Up By Other DRM Drivers

[phoronix]

Phoronix: AMDGPU's Scheduler Might Get Picked Up By Other DRM Drivers

One of the benefits of open-source software is the ability for code re-use by other projects and that may now happen with the AMDGPU kernel driver's scheduler...

http://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-Scheduler-Common

[johanb]

Perfect example on why opensource is awsome!

[schmidtbag]

Perfect example on why opensource is awsome!

Meanwhile, if Rich Geldreich saw this he'd say "see! This is what happens when you open source things!" as though this is a bad thing.

Hopefully, AMD won't see this as inadvertently helping competition.

[vortex]

Meanwhile, if Rich Geldreich saw this he'd say "see! This is what happens when you open source things!" as though this is a bad thing.

Hopefully, AMD won't see this as inadvertently helping competition.

AMD has a history of helping the competition. This is no different.

Though, I think they should leave the function names alone. No need to get rid of AMD_.

[rene]

Meanwhile, if Rich Geldreich saw this he'd say "see! This is what happens when you open source things!" as though this is a bad thing.

Hopefully, AMD won't see this as inadvertently helping competition.

he was / is a small developer that probably did get little to no return for all his weekend research work. I fully understand him, this is not how individual developers and small companies can make a living at all.

[bridgman]

AMD has a history of helping the competition. This is no different.

It works out pretty evenly AFAICS, in the sense that we also benefit quite a bit from work done by other teams.

[Nille]

i guess the developers from this code feel honored. its nice that his own works has a use but its awesome if the work help others too.

[schmidtbag]

he was / is a small developer that probably did get little to no return for all his weekend research work. I fully understand him, this is not how individual developers and small companies can make a living at all.

First of all, he worked for SpaceX, Intel, Unity, Valve, MS, among other established businesses. You don't get around that much if you're a small fry.

Second, he sought out open-source for the sake of getting help, and he got it. Anyone with half a brain knows that once you open-source something, people can and will take advantage of it. He was willfully ignorant of this, he (to my understanding) didn't use any open-source license to protect himself, and as a result, had no right to complain.

Open source is generally only profitable to corporations, not individuals. So yes, it is understandable how it's hard for individuals to make a living off of it. But he made the choice, the nature of open-source worked exactly as it should have, and yet somehow when intentionally opened code is used by others, it's a bad thing. So all that being said, AMD's open-source scheduler became a use to others, which Stach has taken advantage of. He has every right to, and if AMD is graceful enough, they'll be happy about this.


There's a good way to look at how you can treat open-source code that you created:
Think of the people on Instagram, Facebook, or Youtube, when they take a selfie of themselves going out of their way to do a good deed. They're not doing that "for free", they're hoping for more views, congratulations, or maybe even money. People who are genuinely selfless or generous don't beg for attention or compensation for the things they do. The result of your actions should be the reward. If you volunteer or donate, that implies nobody owes you anything. Open-sourcing is effectively a donation of your time and code.

[Holograph]

Is the scheduler considered to be in good shape by the AMD driver devs? I'm a little bit concerned that if this is picked up for generic use that AMD driver devs will have a more difficult time improving it for their own use cases if others start depending on it. Is this a valid concern?

[Guest]

Is the scheduler considered to be in good shape by the AMD driver devs? I'm a little bit concerned that if this is picked up for generic use that AMD driver devs will have a more difficult time improving it for their own use cases if others start depending on it. Is this a valid concern?

And, that's the reason, why developers shouldn't be too eager to get their code mainlined, if the code isn't ready.