Re: [PATCH] Avoid moving tasks when a schedule can be made.

* Ingo Molnar <[email protected]> wrote:

> i think the right approach would be to split up this work into smaller 
> chunks. Or rather, lets first see how this can happen: why is 
> can_migrate() false for so many tasks? Are they all cpu-hot? If yes, 
> shouldnt we simply skip only up to a limit of tasks in this case - 
> it's not like we want to spend 1.5 msecs searching for a cache-cold 
> task which might give us a 50 usecs advantage over cache-hot tasks ...

the only legimate case where we have to skip alot of tasks is the case 
when there are alot of CPU-bound (->cpus_alowed) tasks in the runqueue.  
In that case the scheduler really has to skip that task. But that is not 
an issue in your workload.

	Ingo
-
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: [PATCH] Avoid moving tasks when a schedule can be made.
    • From: Peter Williams <[email protected]>

• References:
  • [PATCH] Avoid moving tasks when a schedule can be made.
    • From: Steven Rostedt <[email protected]>
  • Re: [PATCH] Avoid moving tasks when a schedule can be made.
    • From: Ingo Molnar <[email protected]>

• Prev by Date: [PATCH] extract-ikconfig: don't use --long-options
• Next by Date: Re: [PATCH] Avoid moving tasks when a schedule can be made.
• Previous by thread: Re: [PATCH] Avoid moving tasks when a schedule can be made.
• Next by thread: Re: [PATCH] Avoid moving tasks when a schedule can be made.
• 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]