How does 2.6 SMP scheduler initially assign a thread to a run queue?

In the 2.6 kernel, there is one run queue per CPU, in case of an SMP.
After a thread is created, how does the scheduler determine which run
queue it goes to?  I know that once it goes to a particular run queue,
the scheduler would try to run that thread on that CPU to take
advantage of processor affinity; and then there would be the load
balancing stuff.  But at the very beginning, what algorithm does the
scheduler use to assign a newly created thread to a particulat CPU?
Would the load balancing algorithm be used? Or gang scheduling?
By the way, in an SMT/hyperthreading processor, does the latest kernel
version assign one run queue per physical CPU, or per virtual processor?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: How does 2.6 SMP scheduler initially assign a thread to a run queue?
    • From: "lk" <[email protected]>

• Prev by Date: Re: [Trivial PATCH] new timeofday: move time sources into arch subdirectories
• Next by Date: 2.6.12-rc6-mm1
• Previous by thread: Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM)
• Next by thread: Re: How does 2.6 SMP scheduler initially assign a thread to a run queue?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]