From: Alan.Robinson@ts.fujitsu.com (Alan Robinson)
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Jonathan Davies <Jonathan.Davies@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
George Dunlap <george.dunlap@citrix.com>,
Marcus Granado <marcus.granado@citrix.com>,
Julien Grall <julien.grall@arm.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 3/5] xen: sched: introduce the 'null' semi-static scheduler
Date: Fri, 7 Apr 2017 09:24:02 +0200 [thread overview]
Message-ID: <20170407072402.GA16807@ts.fujitsu.com> (raw)
In-Reply-To: <149152524707.31941.13436906543107118143.stgit@Solace.fritz.box>
On Fri, Apr 07, 2017 at 02:34:07AM +0200, Dario Faggioli wrote:
> In cases where one is absolutely sure that there will be
> less vCPUs than pCPUs, having to pay the cose, mostly in
s/cose/cost/
Alan
--
Alan Robinson
Fujitsu, Enterprise Platform Services, Germany
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-07 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 0:33 [PATCH v2 0/5] The 'null' Scheduler Dario Faggioli
2017-04-07 0:33 ` [PATCH v2 1/5] xen: sched: improve robustness (and rename) DOM2OP() Dario Faggioli
2017-04-07 8:44 ` George Dunlap
2017-04-07 9:05 ` Dario Faggioli
2017-04-07 0:34 ` [PATCH v2 2/5] xen: sched: make sure a pCPU added to a pool runs the scheduler ASAP Dario Faggioli
2017-04-07 8:47 ` George Dunlap
2017-04-07 0:34 ` [PATCH v2 3/5] xen: sched: introduce the 'null' semi-static scheduler Dario Faggioli
2017-04-07 7:24 ` Alan Robinson [this message]
2017-04-07 9:17 ` George Dunlap
2017-04-07 0:34 ` [PATCH v2 4/5] xen: sched_null: support for hard affinity Dario Faggioli
2017-04-07 10:08 ` George Dunlap
2017-04-07 10:11 ` Dario Faggioli
2017-04-07 0:34 ` [PATCH v2 5/5] tools: sched: add support for 'null' scheduler Dario Faggioli
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=20170407072402.GA16807@ts.fujitsu.com \
--to=alan.robinson@ts.fujitsu.com \
--cc=Jonathan.Davies@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=julien.grall@arm.com \
--cc=marcus.granado@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.