this post was submitted on 28 Aug 2023
260 points (94.2% liked)

Linux

48083 readers
785 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
all 20 comments
sorted by: hot top controversial new old
[–] Gurfaild@feddit.de 132 points 1 year ago (4 children)

I FIXED my CAPSLOCK KEY to FINALLY enable CRUISE CONTROL for COOL

[–] Dubious_Fart@lemmy.ml 38 points 1 year ago (1 children)

I can not tell you how many videos and channels I avoid because of that shit.

also ones that have dumb ass thumbnails that do nothing to hint about the content.

[–] featured@lemmy.ml 31 points 1 year ago (2 children)

Agreed, have you tried Dearrow? It’s from the person who created SponsorBlock and is a crowdsourced way to get rid of the clickbait

[–] Dubious_Fart@lemmy.ml 16 points 1 year ago (1 children)

I'd rather just not give the jackasses the attention, than go out of my way to use an app to hide their jackassery

[–] dinckelman@lemmy.world 4 points 1 year ago

I love this addon. It's made my YouTube experience significantly better

[–] LoafyLemon@kbin.social 11 points 1 year ago

BETTER VISIBLE, VISIBLY BETTER

[–] tal@kbin.social 7 points 1 year ago

If the Daily Mail's editors do it, it must be a good idea!

Is this just because of the title, or is the video's content contentless? /gen

[–] yote_zip@pawb.social 41 points 1 year ago* (last edited 1 year ago) (1 children)

"This is on version 4 and approved by many people and it doesn't even work. How was this tested?" types furiously in comic sans

This video is killing me. Very entertaining to share their frustration.

Edit: "When we reach 25k subscribers I will debug the Linux scheduler"

[–] poVoq 10 points 1 year ago

AMD's software has always been in a very sorry state. Only after non-inhouse developers created an alternative GPU driver from scratch for Linux it became feasible to use.

[–] trclst@lemmy.ml 22 points 1 year ago* (last edited 1 year ago)

I am not the creator of the video but amazed what it all makes it into the stable branch.

[–] demonsword@lemmy.world 11 points 1 year ago (2 children)
[–] NoXPhasma@lemmy.world 17 points 1 year ago (1 children)

AMD patches for preferred core (prefer those cores which can clock higher) are a mess and ended up not working because of a wrong if condition. Showing that no one at AMD even tested it before submitting. The programmer in the video complains about AMDs developers being incompetent and shows how it's fixed.

[–] demonsword@lemmy.world 1 points 1 year ago
[–] Olissipo@programming.dev 5 points 1 year ago (1 children)

Apparently there's a bug in an AMD's driver. It was supposed to assign processes based on each core's self reported performance, but because of the bug it was random.

This "self reported performance" is based on evaluation done to the cores in the fab process, by AMD. Meaning, due to imperfections some cores are a bit better than others.

[–] NoXPhasma@lemmy.world 9 points 1 year ago* (last edited 1 year ago) (1 children)

It's not just random, it simply does not even work. Because they set this:

+/*Preferred Core featue is supported*/
+static bool prefcore = true;

And later in the code they do the if condition wrong:

+	if (prefcore)
+		WRITE_ONCE(cpudata->highest_perf, AMD_PSTATE_PREFCORE_THRESHOLD);
+	else
+		WRITE_ONCE(cpudata->highest_perf, AMD_CPPC_HIGHEST_PERF(cap1));

if should look like this:

+	if (prefcore)
+		WRITE_ONCE(cpudata->highest_perf, AMD_CPPC_HIGHEST_PERF(cap1));
+	else
+		WRITE_ONCE(cpudata->highest_perf, AMD_PSTATE_PREFCORE_THRESHOLD);

There is probably even more wrong, looking at the code quality, but this at least makes the preferred core work.

[–] Olissipo@programming.dev 2 points 1 year ago* (last edited 1 year ago) (1 children)

I don't know if we're discussing semantics. A performance score is attributed, and before the fix their scores were all 166. It doesn't work, as you said. So the consequence is the preferred core being "random", isn't it?

[–] NoXPhasma@lemmy.world 1 points 1 year ago

I don't know if it's random, the CPU scheduler still decides what thread to use. It will have its own semantics, but I don't know on what those are based.