From: Meng Xu <xumengpanda@gmail.com>
To: Dario Faggioli <dfaggioli@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Andrii Anisov <andrii_anisov@epam.com>
Subject: Re: RTDS with extra time issue
Date: Fri, 9 Feb 2018 10:36:11 -0500 [thread overview]
Message-ID: <CAENZ-+n1y24akrJZvmkh1eh5exHhr3NQ+33PgjCvNKcFEb74EA@mail.gmail.com> (raw)
In-Reply-To: <1518189527.5019.28.camel@suse.com>
On Fri, Feb 9, 2018 at 10:18 AM, Dario Faggioli <dfaggioli@suse.com> wrote:
>
> On Fri, 2018-02-09 at 17:03 +0200, Andrii Anisov wrote:
> > > If DomR is not able to get its share, then we have an issue/bug in
> > > the
> > > scheduler. If it does, then the scheduler is doing its job, and the
> > > issue may be somewhere else (e.g., something inside the guest may
> > > eat
> > > some of the budget, in such a way that not all of it is available
> > > when
> > > you actually need it).
> >
> > The DomR guest is really lean, I already shown processes list in it.
> > I
> > really doubt init together with getty on HVC can eat another 10% of
> > CPU
> > at any moment.
> >
> So, I'm a little bit in a hurry now, and I'll reply better later (or on
> Monday). But for now, just to understand things better, can you enable
> extratime for DomR as well, and report what you see in xentop, and
> whether or not you still see deadline misses?
>
Another way to check if there is interference from services in domR is
to set period = budget for the domR's VCPUs.
Best Regards,
Meng
-----------
Meng Xu
Ph.D. Candidate in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-09 15:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 12:20 RTDS with extra time issue Andrii Anisov
2018-02-09 12:25 ` Andrii Anisov
2018-02-09 13:18 ` Dario Faggioli
2018-02-09 15:03 ` Andrii Anisov
2018-02-09 15:18 ` Dario Faggioli
2018-02-09 15:36 ` Meng Xu [this message]
2018-02-09 15:56 ` Andrii Anisov
2018-02-09 17:51 ` Meng Xu
2018-02-10 0:14 ` Dario Faggioli
2018-02-10 4:53 ` Meng Xu
2018-02-12 10:17 ` Dario Faggioli
2018-02-12 11:08 ` Andrii Anisov
2018-02-12 14:52 ` Meng Xu
2018-02-12 10:38 ` Andrii Anisov
2018-02-12 10:20 ` Andrii Anisov
2018-02-12 18:44 ` Andrii Anisov
2018-02-16 18:37 ` Dario Faggioli
2018-02-20 11:34 ` Andrii Anisov
2018-02-22 17:53 ` Dario Faggioli
2018-02-26 12:00 ` Andrii Anisov
2018-02-09 15:34 ` Meng Xu
2018-02-09 15:53 ` Andrii Anisov
2018-02-09 16:04 ` Andrii Anisov
2018-02-09 17:53 ` Meng Xu
2018-02-09 18:07 ` Andrii Anisov
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=CAENZ-+n1y24akrJZvmkh1eh5exHhr3NQ+33PgjCvNKcFEb74EA@mail.gmail.com \
--to=xumengpanda@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=dfaggioli@suse.com \
--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.