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:	Tue, 24 Jul 2007 13:47:54 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Chris Snook <csnook@...hat.com>
CC:	Tong Li <tong.n.li@...el.com>, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] scheduler: improve SMP fairness in CFS

Chris Snook wrote:

> Concerns aside, I agree that fairness is important, and I'd really like 
> to see a test case that demonstrates the problem.

One place that might be useful is the case of fairness between resource 
groups, where the load balancer needs to consider each group separately.

Now it may be the case that trying to keep the load of each class within 
X% of the other cpus is sufficient, but it's not trivial.

Consider the case where you have a resource group that is allocated 50% 
of each cpu in a dual cpu system, and only have a single task in that 
group.  This means that in order to make use of the full group 
allocation, that task needs to be load-balanced to the other cpu as soon 
as it gets scheduled out.  Most load-balancers can't handle that kind of 
granularity, but I have guys in our engineering team that would really 
like this level of performance.

We currently use CKRM on an SMP machine, but the only way we can get 
away with it is because our main app is affined to one cpu and just 
about everything else is affined to the other.

We have another SMP box that would benefit from group scheduling, but we 
can't use it because the load balancer is not nearly good enough.

Chris
-
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