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, 02 Apr 2009 13:13:46 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Hitoshi Mitake <h.mitake@...il.com>
Cc:	linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org
Subject: Re: [RFC] Improving scheduler for asymmetric multi-core processor
 in  Google's summer of code

On Wed, 2009-04-01 at 23:58 +0900, Hitoshi Mitake wrote:
> Hi,
> 
> I found an interesting problem, scheduling on Asymmetric multi-core processor.
> 
> According to this paper,
> 
> http://portal.acm.org/citation.cfm?id=1362694&dl=GUIDE&coll=GUIDE&CFID=28487975&CFTOKEN=68150071
> 
> taking performance asymmetry into consideration on multi-core CPUs can
> improve scheduler performance.
> (And I think discarding this could have bad consequences.)
> 
> So I have a question:
> Is the current scheduler of Linux aware of possible performance
> asymmetry of the cores?

It does not.

> By performance asymmetry I mean a case where different cores run on
> different frequencies.
> 
> If something tackling this issue is not implemented yet,
> I would like to work on that as a project of Google's summer of code.

Have at it. 

Its a rather delicate business though and should also include scaling
balancing decisions based on time taken by IRQs and RT tasks as well as
incorporate feedback from the cpu. The latter includes things like
cpufreq, but also effective work done by threads on a core.

Its been on my todo list for quite a while, but haven't managed to get
something robust together.
--
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