Announcement

Collapse
No announcement yet.

Ice Lake Xeons Will Ramp Up Frequencies Slower, So Linux Is Preparing A Workaround

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

  • Ice Lake Xeons Will Ramp Up Frequencies Slower, So Linux Is Preparing A Workaround

    Phoronix: Ice Lake Xeons Will Ramp Up Frequencies Slower, So Linux Is Preparing A Workaround

    While being very eager to learn more about Intel next-gen Ice Lake Xeon processors as their move in the server space finally from 14nm to 10nm+, we continue to learn new tid-bits from the open-source Linux kernel activity...

    http://www.phoronix.com/scan.php?pag...-Frequency-C1E

  • #2
    Non-laptop Ice Lake?! Finally!!!

    Comment


    • #3
      Originally posted by tildearrow View Post
      Non-laptop Ice Lake?! Finally!!!
      They didn't even release an H-class Ice Lake processor.

      Comment


      • #4
        In an ideal world the CPU should be notified if it is an interactive program that requires processing or some background "shit".

        Comment


        • #5
          Originally posted by Raka555 View Post
          In an ideal world the CPU should be notified if it is an interactive program that requires processing or some background "shit".
          On a server, everything is background.

          Comment


          • #6
            Originally posted by starshipeleven View Post
            On a server, everything is background.
            Services with active connections are "interactive" ...

            Comment


            • #7
              On a desktop, another example of "background shit" are browser tabs. Only the active one should be able to clock the CPU above its base clock.
              In fact, personally I would have liked it if the non-active tabs would pause completely.
              Like I said, in an ideal world.
              Last edited by Raka555; 07-15-2020, 06:27 PM.

              Comment


              • #8
                Originally posted by Raka555 View Post
                On a desktop, another example of "background shit" are browser tabs. Only the active one should be able to clock the CPU above its base clock.
                If fact, personally I would have liked it if the non-active tabs would pause completely.
                Like I said, in an ideal world.
                There are extensions which "suspends" tabs which is very useful for older machines with little RAM.

                Unfortunately I don't care about RAM usage but about CPU usage and want them to stay in ram but don't allow any execution from them which as far as I know there's no extensions for. Not sure if it's because it would break lots of webpages or if it's because there's no API for it.

                Comment


                • #9
                  Originally posted by johanb View Post

                  There are extensions which "suspends" tabs which is very useful for older machines with little RAM.

                  Unfortunately I don't care about RAM usage but about CPU usage and want them to stay in ram but don't allow any execution from them which as far as I know there's no extensions for. Not sure if it's because it would break lots of webpages or if it's because there's no API for it.
                  Thanks. I haven't looked at extensions for this in quite some time.
                  I am also not concerned about the RAM usage, but the CPU usage drains the battery on my laptop.
                  I can almost get double the amount of time out of my laptop if I close the browser during power outages.

                  Comment


                  • #10
                    Originally posted by Raka555 View Post
                    In an ideal world the CPU should be notified if it is an interactive program that requires processing or some background "shit".
                    There is support for that in the kernel. Has been there for quite a while.
                    Linux userspace does not make much use of it though.
                    Wakelocking has to be 10 years+. Although not in vanilla.

                    Comment

                    Working...
                    X