Announcement

Collapse
No announcement yet.

AMD GPU Linux Driver Becoming "Really Really Big" That It's Starting To Cause Problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    The hardware doesn't have to be that old. While HDDs are getting increasingly rare in laptops, I could see how a 5400RPM drive (which was relatively common) could struggle to keep up.

    In any case, part of me wonders how much of this GPU code needs to be in the kernel and which could be pushed to userspace.

    Comment


    • #12
      Monolithic kernel continues to bear fruit.

      Comment


      • #13
        Why do you have to reboot a Linux machine?

        Comment


        • #14
          Well, that's one way to solve the problem of bloated closed source software, just make everything else bloated too. Now theres no disadvantage, embrace, extend, extend, extend, extend, extend....

          Comment


          • #15
            Originally posted by aviallon View Post

            Perhaps the time it takes to uncompress the .ko file and load it into memory?
            Even that doesn't take seconds, if you include the firmware.

            Comment


            • #16
              Originally posted by mrg666 View Post
              I wonder if the autogenerated header files can be reduced in number and size by eliminating repeated code.
              <...>
              I just checked Linux 6.10. The size of drivers/gpu/drm/amd is 582 MB, include directory is taking 428MB of it (73.5%).
              I'd rather wonder how on Earth can header files be responsible for the final object size, much less its initialization time.

              Michael doesn't understand systems programming, and apparently y'all don't either.

              Comment


              • #17
                Are they seeing any issues with Nvidia's drivers having the same issue? The amdgpu driver is roughly 4.2mb on my system. Compared to that the nvidia.ko driver is 50mb. Both compressed. If they aren't, then there should be something to improve that without breaking it up.

                Comment


                • #18
                  telling Plymouth to use the SimpleDRM DRM/KMS device instead of waiting for the AMDGPU driver to load. That later option depends upon the PC booting in EFI mode to use SimpleDRM.​
                  Seems like a viable long-term vendor neutral solution that should be the default

                  Comment


                  • #19
                    Originally posted by intelfx View Post

                    I'd rather wonder how on Earth can header files be responsible for the final object size, much less its initialization time.

                    Michael doesn't understand systems programming, and apparently y'all don't either.
                    Where did I say anything about the object size? Try to understand what you read before responding to claim you understand other things better.

                    Comment


                    • #20
                      The amdgpu driver is one the biggest project ever in the Linux Kernel regarding the amount of lines of code it has. I don't want to be ungrateful and I would like to thank the amdgpu developers for their work, but some parts probably needs to get rework. The issue with plymouth is just a minor issue compared to the gpu lockup with ring timeouts. I have this issue at least for 4 years, sometimes rarely, sometimes often. I hope this will be solved in Linux Kernel 6.12 as is mentioned here.

                      Comment

                      Working...
                      X