Announcement

Collapse
No announcement yet.

Many Power Management Updates For The Linux 4.10 Kernel

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

  • Many Power Management Updates For The Linux 4.10 Kernel

    Phoronix: Many Power Management Updates For The Linux 4.10 Kernel

    Rafael Wysocki of Intel on Monday submitted the new ACPI and power management material for the Linux 4.10 merge window. Like most kernel cycles, there is a lot of ACPI/PM improvements on the horizon for Linux...

    http://www.phoronix.com/scan.php?pag...wer-Management

  • #2
    what about TSC which is the default source clock used by linux operating systems on the different machins!? When the cpus implements constant TSC (not invariant) the C1E and or EIST should be disabled!?

    Comment


    • #3
      pstate + schedutil sounds nice

      Comment


      • #4
        Originally posted by davidbepo View Post
        pstate + schedutil sounds nice
        Especially if that helps schedutil to provide the same performance as "performance", when needed.

        I hope the final version of this won't require another flavor of boot parameter ("intel_pstate=passive") as the experimental version apparently did, thereby making all existing options inaccessible. Who would even know about this feature?

        Comment


        • #5
          Originally posted by Azrael5 View Post
          what about TSC which is the default source clock used by linux operating systems on the different machins!? When the cpus implements constant TSC (not invariant) the C1E and or EIST should be disabled!?
          I'm not sure I understand your request: You want the kernel to enforce zero-PM on machines that doesn't support constant TSC?
          Why? Kernel / user-land developers on such platforms should be aware of this limitation and use other clock sources instead of TSC...

          - Gilboa
          DEV: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB + 2x3TB, GTX1080, F24/x86_64, Dell UP3216Q 4K.
          SRV: Intel S5520SC, 2xX5680, 36GB, 4x2TB, GTX550, F24/x86_64, Dell U2711..
          BACK: Tyan Tempest i5400XT, 2xE5335, 8GB, 3x1.5TB, 9800GTX, F24/x86-64.
          LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F24/x86_64.

          Comment


          • #6
            Originally posted by gilboa View Post

            I'm not sure I understand your request: You want the kernel to enforce zero-PM on machines that doesn't support constant TSC? Why? Kernel / user-land developers on such platforms should be aware of this limitation and use other clock sources instead of TSC..
            By the way, would be nice to have a portable userspace lib function around RDTSC as well, if such a thing is possible.
            Last edited by indepe; 12-20-2016, 09:22 AM.

            Comment


            • #7
              Regarding power management:

              It would seem to make sense if threads were able to switch between performance / power-efficient / default modes.

              In default mode, the scaling governor would determine the frequency as it does now.

              In power-efficient mode, a long-running task can run at the frequency optimal for power-consumption, even if its CPU-usage will be 100%.

              In performance mode, it will run at the best available frequency, even if it runs only for short time intervals and averages a low CPU-usage.

              Comment


              • #8
                Originally posted by indepe View Post

                By the way, would be nice to have a portable userspace lib function around RDTSC as well, if such a thing is possible.
                Yeah, but nothing beats having a cross OS / platform / user-mode/kernel-mode ASM library

                - Gilboa
                DEV: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB + 2x3TB, GTX1080, F24/x86_64, Dell UP3216Q 4K.
                SRV: Intel S5520SC, 2xX5680, 36GB, 4x2TB, GTX550, F24/x86_64, Dell U2711..
                BACK: Tyan Tempest i5400XT, 2xE5335, 8GB, 3x1.5TB, 9800GTX, F24/x86-64.
                LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F24/x86_64.

                Comment


                • #9
                  Originally posted by gilboa View Post

                  Yeah, but nothing beats having a cross OS / platform / user-mode/kernel-mode ASM library
                  Too good to be true!

                  Comment


                  • #10
                    Originally posted by indepe View Post

                    Too good to be true!
                    Actually, I have such library for simple stuff, rdtsc, atomic counters, atomic bitmaps, etc.

                    - Gilboa
                    DEV: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB + 2x3TB, GTX1080, F24/x86_64, Dell UP3216Q 4K.
                    SRV: Intel S5520SC, 2xX5680, 36GB, 4x2TB, GTX550, F24/x86_64, Dell U2711..
                    BACK: Tyan Tempest i5400XT, 2xE5335, 8GB, 3x1.5TB, 9800GTX, F24/x86-64.
                    LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F24/x86_64.

                    Comment

                    Working...
                    X