• qaz@lemmy.world
    link
    fedilink
    arrow-up
    107
    ·
    8 months ago

    That’s not to say the two men don’t think AI will be helpful in the future. Indeed, Torvalds noted one good side effect already: “NVIDIA has gotten better at talking to Linux kernel developers and working with Linux memory management,” because of its need for Linux to run AI’s large language models (LLMs) efficiently.

    • umbrella@lemmy.ml
      link
      fedilink
      arrow-up
      83
      ·
      edit-2
      8 months ago

      so THATS why we are getting better nvidia support.

      i knew it just couldnt be from the goodness of their newly converted hearts.

      • Miaou@jlai.lu
        link
        fedilink
        arrow-up
        7
        arrow-down
        3
        ·
        8 months ago

        You didn’t know GPUs are used for training/running DNN?

        • umbrella@lemmy.ml
          link
          fedilink
          arrow-up
          19
          arrow-down
          1
          ·
          8 months ago

          sure, but am i surprised this is the only reason they improved desktop drivers for us? no.

          am i disappointed? yeah, a little.

  • Nemoder@lemmy.ml
    link
    fedilink
    arrow-up
    44
    ·
    8 months ago

    Hohndel agreed but added that the industry needs to support these smaller projects – and not only with money. “Companies need to engage with these projects. Have your company adopt a couple of such projects and just participate. Read the code, review the patches, and provide moral support to the maintainers. It’s as simple as that.”

    Really glad he said this, I keep seeing posts about how all these big companies could solve the problem by just throwing money at small projects and while that is better than nothing it would help way more to have their own developers helping to review and fix issues.

  • vort3@lemmy.ml
    link
    fedilink
    arrow-up
    20
    ·
    8 months ago

    Is there a link to this talk (or interview, or whatever this is) but in a video format, or at least a text without all those «SEE ALSO» self ads?

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    8
    ·
    8 months ago

    Does anyone have the link for the source of the interview? I’ve looked through the article and couldn’t see it at first glance.

    • liara@lemm.ee
      link
      fedilink
      English
      arrow-up
      12
      ·
      8 months ago

      Open Source Summit 2024 keynotes. I don’t think any of the recordings are available yet.

        • liara@lemm.ee
          link
          fedilink
          English
          arrow-up
          3
          ·
          8 months ago

          It literally was in the opening paragraph. Previous years keynotes are available in a playlist here, so I assume they’ll do the same for this year’s keynotes as well. The event only just ended yesterday.

          • thingsiplay@beehaw.org
            link
            fedilink
            arrow-up
            4
            ·
            8 months ago

            It literally was in the opening paragraph.

            No, I mean they should have disclosed this talk/interview not being ready to the public consumption. Clicking the link just opened up the webpage and I was lost, expecting the watch or read the interview. There is no mention of this being not available yet, despite the link. That’s what I mean being confusing. It’s not the end of the world, and it would also not be the end of the world if they added a note after the link like “(note: talk is not available to watch for the public yet)”.

          • PipedLinkBot@feddit.rocksB
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 months ago

            Here is an alternative Piped link(s):

            here

            Piped is a privacy-respecting open-source alternative frontend to YouTube.

            I’m open-source; check me out at GitHub.

  • hungrybread [comrade/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    6
    ·
    8 months ago

    In addition, hardware developers reinvent old ways of doing things and only learn by making all the same mistakes that have been made before. It’s sad, but true.

    This same criticism is validly launched at software devs all the time lol.

    One thing I’ve anecdotalally seen and heard is hardware guys indicating that something is rock solid and solved because it’s old, so building on top of it isn’t a problem. Obviously we have to build on the old to get to the new, but if we just skip auditing hardware due to age we end up deploying vulnerable hardware globally. Spectre and Meltdown are an interesting example where I’ve heard from at least one distinguished professor that “everyone” believed branch prediction design/algorithms were essentially done. Was it adequately assessed from a security POV? Clearly not, but was it assessed from a security POV in general? I have no idea, but it would be nice as a tech enthusiast and software guy to see the other side of the fence take these things seriously in a more public way, in particular when it comes to assessing old hardware for new attack vectors.

    • lemmyreader@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 months ago

      Spectre and Meltdown are an interesting example where I’ve heard from at least one distinguished professor that “everyone” believed branch prediction design/algorithms were essentially done.

      Interesting to hear this.

      Was it adequately assessed from a security POV? Clearly not, but was it assessed from a security POV in general? I have no idea, but it would be nice as a tech enthusiast and software guy to see the other side of the fence take these things seriously in a more public way, in particular when it comes to assessing old hardware for new attack vectors.

      Right.