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-next>] [day] [month] [year] [list]
Message-ID: <6e782fa5-de1d-93a9-ed11-5b43b65b20c9@huawei.com>
Date:   Mon, 30 Jul 2018 20:08:55 +0800
From:   "weiqi (C)" <weiqi4@...wei.com>
To:     <linux-kernel@...r.kernel.org>, <peterz@...radead.org>
CC:     Zhanghailiang <zhang.zhanghailiang@...wei.com>
Subject: [Question] load balance move tasks not suitable ?

Hi Peter,

After  Commits 5d6523ebd(sched: Fix load-balance wreckage),
The jugement whether imbalance reached changed from twice to one-half.

from

(1) if((load * 2)> rem_load_move)
         goto next;

to

(2) if((load / 2)> env-> load_move)
         goto next;

I'm confused about this change.

"load*2" may be more appropriate, because if a task whose load more than 
env->imbalance is moved from high load cpu to low load cpu,

will make more imbalance.

Regards,

Content of type "text/html" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ