mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Hitoshi Mitake <h.mitake@gmail.com>
Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: [RFC] Improving scheduler for asymmetric multi-core processor in  Google's summer of code
Date: Thu, 02 Apr 2009 13:13:46 +0200	[thread overview]
Message-ID: <1238670826.8530.5837.camel@twins> (raw)
In-Reply-To: <a6b9f31a0904010758r23767adco16ea4ee45d7e158e@mail.gmail.com>

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.

  reply	other threads:[~2009-04-02 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 14:58 Hitoshi Mitake
2009-04-02 11:13 ` Peter Zijlstra [this message]
2009-04-02 11:53   ` Hitoshi Mitake
     [not found]     ` <dc864f960904020946y5fcebfdfy7679d2bd9ab3dc5e@mail.gmail.com>
2009-04-03 14:51       ` Hitoshi Mitake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1238670826.8530.5837.camel@twins \
    --to=peterz@infradead.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=h.mitake@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®