linux-kernel - Re: Scheduling the highest priority task

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Aug 2007 17:19:16 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Martin Roehricht <ml@...icis.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Scheduling the highest priority task


* Martin Roehricht <ml@...icis.org> wrote:

> That's fine with me, that within the same priority-queue any task can 
> be chosen. But assume two tasks with highly different priorities, such 
> as 105 and 135 are scheduled on the same processor and one of them is 
> now to be migrated -- shouldn't be the queue with task P=105 
> considered first for migration by this code? Both tasks would use 
> different queues with their own linked lists, right?

yes. What makes you believe that the lower priority one (prio 135) is 
chosen? [ as i said before, that will only be chosen if all tasks in the 
higher-priority queue (prio 105) are either already running on a CPU or 
have recently run so that the cache-hot logic skips them. ]

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