Talk:Processor affinity

Old information, maybe?

"For example, a system with two dual-core hyper-threaded CPUs presents a challenge to a scheduling algorithm. " in the Usage section. Is it still true? Nowadays practically all processors are multicore and multithreaded, at least for PCs and smartphones. Someone who actually has knowledge on computer science needs to update this, because I'm not qualified enough.Felipe lorenzzon (talk) 13:43, 8 June 2021 (UTC)[reply]

Just because something is common doesn't mean it's not a challenge. It may be a challenge for which there are now known solutions, but those solutions may still require complicated code.
The full quote is

Also note that processor affinity becomes more complicated in systems with non-uniform architectures. For example, a system with two dual-core hyper-threaded CPUs presents a challenge to a scheduling algorithm.

and a system with two dual-core threaded processors is non-uniform as, in the simplest model, a system with two dual-core two-thread processors has has eight pseudo-CPUs running in parallel, but it really has:
  • two independent CPU chips;
  • on each CPU chip, two separate CPU cores;
  • on each CPU core, the ability to run two threads of control in parallel, in a fashion that usually allows software to treat the two threads of control as two pseudo-CPUs.
A naive scheduler would treat such a system as an eight-way SMP system, scheduling all eight pseudo-CPUs as independent processors. However:
  • the two cores on the same CPU may share some elements, such as a level 2 cache, but two cores on different CPUs don't share as many elements, so running two processes on cores on separate CPUs may differ in performance from running two processes on cores on the same CPU;
  • a thread is a pseudo-CPU, with the two threads on a single core share most of the hardware of that core, so running two processes on separate cores may differ in performance from running two processes on two threads of a single core.
and a scheduler might want to take that into account. Guy Harris (talk) 20:51, 8 June 2021 (UTC)[reply]

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.