From: Wei Liu <wei.liu2@citrix.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
wei.liu2@citrix.com, "Yu-An(Victor) Chen" <chen116@usc.edu>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen 4.5.0 rtds scheduler perform poorly with 2vms
Date: Wed, 2 Dec 2015 10:54:51 +0000 [thread overview]
Message-ID: <20151202105451.GB25722@citrix.com> (raw)
In-Reply-To: <CAENZ-+nQMa-n0u8spOoLOFmBOXf3H-pokP9NQaaQRP+WCrzoww@mail.gmail.com>
On Tue, Dec 01, 2015 at 11:54:14PM -0600, Meng Xu wrote:
> Hi Lars and Dario,
>
> 2015-12-01 4:11 GMT-06:00 Lars Kurth <lars.kurth.xen@gmail.com>:
> >
> > I wonder whether we need to add some health warnings and recommended background reading to http://wiki.xenproject.org/wiki/RTDS-Based-Scheduler
>
>
> Maybe we could add some health warning and add a link to this discussion?
> Misconfiguration of the system will usually cause performance
> degradation, even for the other schedulers, such as ARINC653, credit,
> credit2.
> What I'm thinking is how much expert information we should expose to
> users. Sometimes, exposing too much information may not be so helpful.
> Sometimes, more information just cause more confusion.
>
> What do you guys think which type of information we should include?
>
Wiki and xl manpage ?
Wei.
next prev parent reply other threads:[~2015-12-02 10:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 15:42 xen 4.5.0 rtds scheduler perform poorly with 2vms Yu-An(Victor) Chen
2015-11-23 16:07 ` Meng Xu
2015-11-23 16:35 ` Yu-An(Victor) Chen
2015-11-24 2:23 ` Meng Xu
2015-11-24 4:57 ` Yu-An(Victor) Chen
2015-11-24 6:19 ` Meng Xu
2015-11-25 0:15 ` Dario Faggioli
2015-11-27 16:36 ` Yu-An(Victor) Chen
2015-11-27 17:23 ` Dario Faggioli
2015-11-27 17:41 ` Meng Xu
2015-11-27 19:50 ` Yu-An(Victor) Chen
2015-11-28 0:17 ` Meng Xu
2015-11-28 12:20 ` Yu-An(Victor) Chen
2015-11-28 15:09 ` Meng Xu
2015-11-29 12:46 ` Yu-An(Victor) Chen
2015-11-29 15:38 ` Meng Xu
2015-11-29 16:27 ` Dario Faggioli
2015-11-29 16:44 ` Meng Xu
2015-11-29 18:16 ` Yu-An(Victor) Chen
2015-12-01 8:59 ` Dario Faggioli
2015-12-01 10:11 ` Lars Kurth
2015-12-01 16:01 ` Yu-An(Victor) Chen
2015-12-02 5:54 ` Meng Xu
2015-12-02 10:54 ` Wei Liu [this message]
2015-12-02 11:01 ` Ian Campbell
2015-12-02 11:27 ` Dario Faggioli
2015-12-02 11:03 ` Lars Kurth
2015-12-02 11:19 ` Dario Faggioli
2015-12-02 16:57 ` Meng Xu
2015-11-29 16:18 ` Dario Faggioli
2015-11-29 16:21 ` Meng Xu
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=20151202105451.GB25722@citrix.com \
--to=wei.liu2@citrix.com \
--cc=chen116@usc.edu \
--cc=dario.faggioli@citrix.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@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.