All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Paul Turner <pjt@google.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Benjamin Segall <bsegall@google.com>,
	Ranjit Manomohan <ranjitm@google.com>,
	Nikhil Rao <ncrao@google.com>,
	jmc@cs.unc.edu, Dhaval Giani <dhaval.giani@gmail.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] LinSched for v3.3-rc7
Date: Fri, 23 Mar 2012 12:03:42 +0800	[thread overview]
Message-ID: <4F6BF61E.7000009@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAPM31RL6Sk6cNR9MzW_7XDvfkMA1q6xK_mcJJaCMY8Ex___9+A@mail.gmail.com>

On 03/15/2012 11:58 AM, Paul Turner wrote:

> Hi All,
> 
> [ Take 2, gmail tried to a non text/plain component into the last email .. ]
> 
> Quick start version:
> 
> Available under linsched-alpha at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjt/linsched.git  .linsched

Hi, All

I got confused with the LinSched main loop...
My understanding is:

	while (not time up) {
		
		get all cpus whose next event is the left most
		
		for those cpus {

			simulate hres clock interrupt		
			
			process_all_softirqs() ?			

			if cpu is idle
				enter idle
			else
				check process running time
		}
	}

Wonder why we need to call process_all_softirqs which will process other
cpu's pending soft irq here?

Regards,
Michael Wang


  parent reply	other threads:[~2012-03-23  4:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  3:58 [ANNOUNCE] LinSched for v3.3-rc7 Paul Turner
2012-03-15  4:08 ` Dhaval Giani
2012-03-21  9:20   ` Michael Wang
2012-03-21  9:54     ` Paul Turner
2012-03-21 10:11       ` Michael Wang
2012-03-21 14:20   ` Morten Rasmussen
2012-03-15  7:21 ` Ingo Molnar
2012-03-23  4:03 ` Michael Wang [this message]
2012-03-28  5:19   ` Michael Wang
2012-04-09  3:29 ` Michael Wang
2012-07-23  3:03 ` Michael Wang
2012-07-23 12:54   ` Paul Turner

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=4F6BF61E.7000009@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=bsegall@google.com \
    --cc=dhaval.giani@gmail.com \
    --cc=jmc@cs.unc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ncrao@google.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=ranjitm@google.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@in.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.