73
Disabling Intel Graphics Security Mitigations Can Boost GPU Compute Performance By 20% (www.phoronix.com)
submitted 1 year ago by to c/linux@lemmy.ml
2 comments fedilink hide all child comments

all 2 comments

sorted by: hot top controversial new old
[–] 13 points 1 year ago (1 child)

Rawdogging saves the time of putting on a condom.
More news at seven.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • 7 comments in c/linux@programming.dev view that post
    [–] 8 points 1 year ago (1 child)

    I've seen this being recommended for audio production but was put off disabling it because I didn't understand what it was. I'd like the performance gain though.

    Has anyone else here disabled it?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago*

    The common sketchy performance advice is to disable mitigations in the kernel, this post is about disabling mitigations in Intel's userspace graphics stack because it's already checked in the kernel.

    Assuming you meant disabling kernel mitigations, since AFAIK audio stuff doesn't usually use OpenCL:

    Has anyone else here disabled it?

    Nah, my understanding is it's not worth it on newer CPUs, and in some cases, the microcode expects things to be mitigated for best performance. Older CPUs (pre-2019ish) it does make a difference though.

    But you're welcome to benchmark it, and see if it makes a worthwhile difference on your CPU. Kernel mitigations are easy enough to turn on and off.

  • permalink
  • fedilink
  • source
  • parent
    • [+] -9 points 1 year ago (4 children)

    I know you think you're doing the lord's work by reposting everything from !linux@lemmy.ml but all it ends up doing is polluting my feed quite a bit. There were always crossposts between the two but there was good reason to subscribe to both. Now it's just two of everything, and there's more engagement over there so I'm more likely to drop this one... ¯\_(ツ)_/¯

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 11 points 1 year ago* (2 children)

    Context:

    Why am I cross-posting .ml?

    I cross-post from .ml to the nearest relevant non-.ml comm to reduce the influence of .ml comms and indirectly, the instance as a whole, to make it an easier decision for other instance admins to defederate because one key reason I identified that admins don't want to defederate is because .ml still has some very large comms and some niche comms.

    Megathread on the issue

    Some highlights from the link:

    "Don't worry guys, the Uyghur Genocide was REALLY just birth control! ~dessalines, .ml admin, dev https://lemmy.world/post/30580167

    "See! nobody died IN Tiananmen Square, just AROUND it, so it doesn't count!!" ~ Davel, .ml admin https://lemmy.world/post/30673342

    .ml admin, Nutomics continued transphobia https://lemmy.world/post/29222558

    CW: Original transphobic Comment from Nutomic

    And so so much documentation on clear heavy handed censorship and bias also on the link. So much I can't even put them all here because this comment would be really long.

    I believe the behavior of its admins (the main admins are Lemmy devs) does harm to the overall growth of the Lemmy-verse and maybe even the Thrediverse (since Lemmy kinda kicked off the Thrediverse) because of its association with the devs of Lemmy and their insistence to use .ml as their personal political platform to spread harmful propaganda

    On the outside, bringing up Lemmy frequently leads to comments like "Lemmy? Isn't that the place with a bunch of tankies?" Or "Tried Lemmy, but found it full of pro Russia crap so I left". The best way forward from that I see is to either widely defederate from .ml like the rest of the Triad, or pressure them to put a fair and unbiased as possible admin team.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -5 points 1 year ago (1 child)

    I know why you're doing it. Trying to mirror the third-largest comm on all of Lemmy is quite the task though, but you do you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 1 year ago* (last edited 1 year ago)

    I'm glad they're bringing some posts that are also on .ml to here. It's an incredibly toxic instance with mods/admins that will harass and ban people a shitload, particularly if they're not aggressively pro-tankie.

    I received a 12 month ban across all of lemmy.ml for saying it's probably a wise thing that sanctioned, state-affiliated Russian companies aren't allowed employees in maintainer roles for the Linux kernel. The mods there are fucking psychos.

    Decentralisation is one of the good parts of Lemmy. I like that I can opt out of lemmy.ml idiocy without entirety alienating myself.

  • permalink
  • fedilink
  • source
  • parent
    • 2 comments in c/hardware@lemmy.world view that post
    [–] 3 points 1 year ago

    "After discussion between Intel and Canonical’s security teams, we are in agreement that Spectre no longer needs to be mitigated for the GPU at the Compute Runtime level. At this point, Spectre has been mitigated in the kernel, and a clear warning from the Compute Runtime build serves as a notification for those running modified kernels without those patches. For these reasons, we feel that Spectre mitigations in Compute Runtime no longer offer enough security impact to justify the current performance tradeoff."

    Seems like the Spectre mitigations were applied for GPU compute as well.

    1 to 5 percentage points is not great, but in and around the margin of error. 20% is a huge performance delta.

  • permalink
  • fedilink
  • source
    •
    [–] 0 points 1 year ago

    20 % of shit is still shit.

    Luckily my Intel GPU is lacking so many features that it barely has to do anything at all.

  • permalink
  • fedilink
  • source
    •