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:	Sat, 10 Oct 2015 11:59:41 +0800
From:	Wanpeng Li <wanpeng.li@...mail.com>
To:	paul.szabo@...ney.edu.au, Peter Zijlstra <peterz@...radead.org>
CC:	Mike Galbraith <umgwanakikbuti@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: CFS scheduler unfairly prefers pinned tasks

Hi Paul,
On 10/8/15 4:19 PM, Mike Galbraith wrote:
> On Tue, 2015-10-06 at 04:45 +0200, Mike Galbraith wrote:
>> On Tue, 2015-10-06 at 08:48 +1100, paul.szabo@...ney.edu.au wrote:
>>> The Linux CFS scheduler prefers pinned tasks and unfairly
>>> gives more CPU time to tasks that have set CPU affinity.
>>> This effect is observed with or without CGROUP controls.
>>>
>>> To demonstrate: on an otherwise idle machine, as some user
>>> run several processes pinned to each CPU, one for each CPU
>>> (as many as CPUs present in the system) e.g. for a quad-core
>>> non-HyperThreaded machine:
>>>
>>>    taskset -c 0 perl -e 'while(1){1}' &
>>>    taskset -c 1 perl -e 'while(1){1}' &
>>>    taskset -c 2 perl -e 'while(1){1}' &
>>>    taskset -c 3 perl -e 'while(1){1}' &
>>>
>>> and (as that same or some other user) run some without
>>> pinning:
>>>
>>>    perl -e 'while(1){1}' &
>>>    perl -e 'while(1){1}' &
>>>
>>> and use e.g.   top   to observe that the pinned processes get
>>> more CPU time than "fair".

Interesting, I can reproduce it w/ your simple script. However, they are 
fair when the number of pinned perl tasks is equal to unpinned perl 
tasks. I will dig into it more deeply.

Regards,
Wanpeng Li
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ