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]
Message-ID: <20070725191848.GB4463@elte.hu>
Date:	Wed, 25 Jul 2007 21:18:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Li, Tong N" <tong.n.li@...el.com>
Cc:	linux-kernel@...r.kernel.org, Chris Snook <csnook@...hat.com>
Subject: Re: [RFC] scheduler: improve SMP fairness in CFS


* Li, Tong N <tong.n.li@...el.com> wrote:

> The problem I see is that the current load balancing code is quite 
> hueristic and can be quite inaccurate sometimes. Its goal is to 
> maintain roughly equal load on each core, where load is defined to be 
> the sum of the weights of all tasks on a core. If all tasks have the 
> same weight, this is a simple problem. If different weights exist, 
> this is an NP-hard problem and our current hueristic can perform badly 
> under various workloads. A simple example, if we have four tasks on 
> two cores and they have weights 1, 5, 7, 7. The balanced partition 
> would have 1 and 7 on core 1 and 5 and 7 on core 2. But you can see 
> the load isn't evenly distributed; in fact, it's not possible to 
> evenly distribute the load in this case. Thus, my opinion is that only 
> balancing the load as we do now is not enough to achieve SMP fairness. 
> My patch was intended to address this problem.

could you please try my patch nevertheless and see how much it differs 
in practice from your solution, and cite specific examples and 
measurements? (please measure over longer periods of time such as 120 
seconds or 300 seconds - so that slow-rate balancing has its chance to 
work)

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ