Announcement

Collapse
No announcement yet.

Partial SMT Enablement Support Lands For Linux 6.6

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

  • Partial SMT Enablement Support Lands For Linux 6.6

    Phoronix: Partial SMT Enablement Support Lands For Linux 6.6

    As part of the "smp/core" changes that were merged last week for the Linux 6.6 kernel, partial SMT enablement landed for processors that support more than two threads per physical core to allow greater run-time control over just how many threads to enable...

    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
    Intel must have an internal patch somewhere that they use.

    They just recently demoed a non-x86 8 core RISC chip that can process 66 threads per core.

    Comment


    • #3
      Originally posted by ezst036 View Post
      Intel must have an internal patch somewhere that they use.

      They just recently demoed a non-x86 8 core RISC chip that can process 66 threads per core.

      Comment


      • #4
        Originally posted by ezst036 View Post
        Intel must have an internal patch somewhere that they use.

        They just recently demoed a non-x86 8 core RISC chip that can process 66 threads per core.
        The are made for for a certain type of graph traversal that is doing a memory load or branching every 3-6 instructions. Where 1-2 threads you'd sit idle 98% of the time, and a GPU would choke on too many instruction branches.

        Comment


        • #5
          Originally posted by WorBlux View Post

          The are made for for a certain type of graph traversal that is doing a memory load or branching every 3-6 instructions. Where 1-2 threads you'd sit idle 98% of the time, and a GPU would choke on too many instruction branches.
          That makes a lot of sense, given memory latency to system memory is around 80-150 cycles, if you have 66 threads you can keep the execution engine busy so long as several are serviced per cycle it can keep a fairly wide execution engine busy. Such a system is usually very undesirable for interactive use though. Also the execution engine can potentially get picky and only service threads that have the most data available etc...

          Comment

          Working...
          X