Announcement

Collapse
No announcement yet.

Intel Performance Limit Reasons For Linux To Report Why Your CPU Is Downclocking

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

  • Intel Performance Limit Reasons For Linux To Report Why Your CPU Is Downclocking

    Phoronix: Intel Performance Limit Reasons For Linux To Report Why Your CPU Is Downclocking

    Intel Performance Limit Reasons (PLR) can indicate why your CPU is downclocking / limited to a lower performance limit for a given core or die. With some Windows utilities this information this Intel CPU feature has been available there while now Intel is bringing PLR support to Linux too...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Torvalds freakout about yet another Intel three-letter acronym in 3, 2, 1...

    Comment


    • #3
      Originally posted by mxan View Post
      Torvalds freakout about yet another Intel three-letter acronym in 3, 2, 1...
      I'm 100% against new acronyms/abbreviations for /sys or anywhere else in Linux for that matter.

      We are in 2024 for Christ's sake. The worst embedded devices now come with at least 128MB of RAM - there's enough memory to use complete English words.

      Comment


      • #4
        1. Too hot
        2. Much too hot
        3. Roasting

        Comment


        • #5
          Wow, I sure hope this gets added to turbostat!

          Comment


          • #6
            Originally posted by avis View Post
            I'm 100% against new acronyms/abbreviations for /sys or anywhere else in Linux for that matter.
            I pretty much agree. Names should be clear, unambiguous, and the shortest names/abbreviations/initialisms should generally be reserved for the most frequent and fundamental concepts (similar idea to Huffman coding). Along these lines, I also tend to make type names longer than variable names, as type name have less locality and variable names are referenced more frequently.



            Naming Things: The Hardest Problem in Software Engineering [Benner, Tom] on Amazon.com. *FREE* shipping on qualifying offers. Naming Things: The Hardest Problem in Software Engineering


            Originally posted by avis View Post
            We are in 2024 for Christ's sake. The worst embedded devices now come with at least 128MB of RAM - there's enough memory to use complete English words.
            It's not about memory, but typing and screen space. Especially if you're using some antiquated 80 column line length limit, long names become rather problematic. I'd approach these issues from both sides. First, a modest increase in maximum line length, accepting that many of us like to view files & diffs side-by-side, so maybe still don't go too much above 100 columns. Then, an accepted dictionary of abbreviations, so we aren't typing out entire words like "performance", when literally nobody would mistake "perf" for anything other than that.

            Comment


            • #7
              Originally posted by pWe00Iri3e7Z9lHOX2Qx View Post
              1. Too hot
              2. Much too hot
              3. Roasting
              Those sound like the performance level names that Intel Marketing decided not to use.

              Comment


              • #8
                Originally posted by pWe00Iri3e7Z9lHOX2Qx View Post
                1. Too hot
                2. Much too hot
                3. Roasting
                • Too hot
                • Too cheap
                • Too old
                • Too new

                Comment


                • #9
                  Brought to you by the brilliant tech corporation, which believes the solution to its inability to design good chips is adopting next gen lytho equipment before it is economically viable, and its most competitive strategy has been to outbid amd for production capacity and waste it producing junk nobody wants...

                  Comment


                  • #10
                    Originally posted by ddriver View Post
                    Brought to you by the brilliant tech corporation, which believes the solution to its inability to design good chips is adopting next gen lytho equipment before it is economically viable,
                    Huh? Intel's 10 nm node (AKA "Intel 7") is DUV, while TSMC and Samsung had already moved on to EUV. Intel didn't reach EUV until "Intel 4", first seen in the underwhelming Meteor Lake.

                    Comment

                    Working...
                    X