From: Yuyang Du <yuyang.du@intel.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"morten.rasmussen@arm.com" <morten.rasmussen@arm.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Cox, Alan" <alan.cox@intel.com>
Subject: Re: [RFC II] Splitting scheduler into two halves
Date: Fri, 28 Mar 2014 07:00:22 +0800 [thread overview]
Message-ID: <20140327230022.GA27225@intel.com> (raw)
In-Reply-To: <1395989431.4877.19.camel@marge.simpson.net>
On Fri, Mar 28, 2014 at 07:50:31AM +0100, Mike Galbraith wrote:
> On Fri, 2014-03-28 at 06:13 +0800, Yuyang Du wrote:
>
> > Spitting does feel brutal...
>
> FWIW, "split" stuck hard in my gullet because task placement is core
Oh, sorry for that, :)
> fastpath mission. If the fastpath could afford to and did task
> placement perfectly, task placement EDC (if you will) mechanisms would
> not exist.
Sometimes, we have to if not get to.
Yuyang
next prev parent reply other threads:[~2014-03-28 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 18:37 [RFC II] Splitting scheduler into two halves Yuyang du
2014-03-27 4:57 ` Mike Galbraith
2014-03-27 7:25 ` Ingo Molnar
2014-03-27 22:13 ` Yuyang Du
2014-03-28 6:50 ` Mike Galbraith
2014-03-27 23:00 ` Yuyang Du [this message]
2014-03-28 7:05 ` Mike Galbraith
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=20140327230022.GA27225@intel.com \
--to=yuyang.du@intel.com \
--cc=alan.cox@intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=umgwanakikbuti@gmail.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.