From: Andrii Anisov <andrii.anisov@gmail.com>
To: Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: arm: xl vcpu-pin leads to oom-killer slashing processes
Date: Wed, 5 Dec 2018 12:59:41 +0200 [thread overview]
Message-ID: <9f2f6edf-c96d-fda9-851b-a2bae8fb25ec@gmail.com> (raw)
In-Reply-To: <cfad156f-19ef-5e87-7af0-3dbbf361dc8a@arm.com>
Hello Julien,
On 05.12.18 12:49, Julien Grall wrote:
> I am not sure to understand what is the relation between the two.
Me confused as well. I just notified about my observations.
> What is the latest Xen commit where the oom-killer does not trigger?
I didn't bisect it nor digged into it. I'm trying to measure IRQ latency as Stefano did.
> How much memory do you have in Dom0? Do you have any memory hungry process running?
Dom0 has 3Gb RAM. But it's not about the memory, I'm pretty sure. Until I decided to pin vcpus, I did all my routine without any issues.
--
Sincerely,
Andrii Anisov.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-05 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:26 arm: xl vcpu-pin leads to oom-killer slashing processes Andrii Anisov
2018-12-05 10:28 ` Andrii Anisov
2018-12-05 10:49 ` Julien Grall
2018-12-05 10:59 ` Andrii Anisov [this message]
2018-12-05 11:45 ` Julien Grall
2018-12-05 11:59 ` Andrii Anisov
2018-12-05 12:15 ` Julien Grall
2018-12-05 12:40 ` Andrii Anisov
2018-12-05 13:13 ` Julien Grall
2018-12-05 14:46 ` Andrii Anisov
2018-12-13 14:13 ` Andrii Anisov
2018-12-13 16:37 ` Juergen Gross
2018-12-14 10:36 ` 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=9f2f6edf-c96d-fda9-851b-a2bae8fb25ec@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=julien.grall@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).