From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org, dpsmith@apertussolutions.com
Subject: Re: [xen-unstable test] 164996: regressions - FAIL
Date: Wed, 22 Sep 2021 15:26:49 +0200 [thread overview]
Message-ID: <54b1b5be-9f43-9513-d274-105d28bd5a58@suse.com> (raw)
In-Reply-To: <24907.8642.479155.35952@mariner.uk.xensource.com>
On 22.09.2021 14:29, Ian Jackson wrote:
> I'm not sure, though, that I fully understand the design principles
> behind non-order-0 allocations, and memory sizing, and so on. Your
> earlier mail suggeted there may not be a design principle, and that
> anything relying on non-order-0 atomic allocations is only working by
> luck (or an embarassing excess of ram).
That's what I think, yes. During boot and in certain other specific
places it may be okay to use such allocations, as long as failure
leads to something non-destructive. A process (or VM) not getting
created successfully _might_ be okay; a process or VM failing when
it already runs is not okay. Just to give an example. The situation
here falls in the latter category, at least from osstest's pov. IOW
assuming that what gets tested is a goal in terms of functionality,
VM creation failing when there is enough memory (just not in the
right "shape") is not okay here. Or else the test was wrongly put
in place.
Therefore a goal I've been trying to follow in the hypervisor is to
eliminate higher order allocations wherever possible. And I think
the kernel wants to follow suit here.
Jan
next prev parent reply other threads:[~2021-09-22 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 4:06 [xen-unstable test] 164996: regressions - FAIL osstest service owner
2021-09-16 16:21 ` Jan Beulich
2021-09-20 15:44 ` Ian Jackson
2021-09-20 15:58 ` Jan Beulich
2021-09-21 23:38 ` Stefano Stabellini
2021-09-22 7:34 ` Jan Beulich
2021-09-22 11:20 ` Ian Jackson
2021-09-22 12:24 ` Jan Beulich
2021-09-22 12:29 ` Ian Jackson
2021-09-22 13:26 ` Jan Beulich [this message]
2021-09-23 1:10 ` Stefano Stabellini
2021-09-23 2:56 ` Julien Grall
2021-09-28 15:24 ` Jan Beulich
2021-09-28 16:16 ` Ian Jackson
2021-09-29 21:35 ` Ian Jackson
2021-10-04 15:22 ` Ian Jackson
2021-09-23 9:24 ` Jan Beulich
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=54b1b5be-9f43-9513-d274-105d28bd5a58@suse.com \
--to=jbeulich@suse.com \
--cc=dpsmith@apertussolutions.com \
--cc=iwj@xenproject.org \
--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.