From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Andres Lagar-Cavilla <andreslc@gridcentric.ca>
Cc: "Keir (Xen.org)" <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Proposed XENMEM_claim_pages hypercall: Analysis of problem and alternate solutions
Date: Thu, 3 Jan 2013 10:49:49 -0800 (PST) [thread overview]
Message-ID: <d6b1ecdd-0a6c-4059-bfdf-a32ffb55e8da@default> (raw)
In-Reply-To: <500D325B-D5C1-4030-8B2F-749646ED426B@gridcentric.ca>
> From: Andres Lagar-Cavilla [mailto:andreslc@gridcentric.ca]
> On Jan 2, 2013, at 4:43 PM, Dan Magenheimer <dan.magenheimer@oracle.com> wrote:
> > I reject the omnisicient toolstack model as unimplementable [1]
> > and, without it, I think you either do need a separate allocation/list,
> > with all the issues that entails, or you need the proposed
> > XENMEM_claim_pages hypercall to resolve memory allocation races
> > (i.e. vs domain creation).
>
> That pretty much ends the discussion. If you ask me below to reason within the constraints your
> rejection places, then that's artificial reasoning. Your rejection seems to stem from philosophical
> reasons, rather than technical limitations.
Well, perhaps my statement is a bit heavy-handed, but I don't see
how it ends the discussion... you simply need to prove my statement
incorrect! ;-) To me, that would mean pointing out any existing
implementation or even university research that successfully
predicts or externally infers future memory demand for guests.
(That's a good approximation of my definition of an omniscient
toolstack.)
But let's save that for another time or thread.
> Look, your hyper call doesn't kill kittens, so that's about as far as I will go in this discussion.
Noted. I will look at adding kitten-killing functionality
in the next revision. ;-)
> My purpose here was to a) dispel misconceptions about sharing b) see if something better comes out
> from a discussion between all interested mm parties. I'm satisfied insofar a).
At some time I hope to understand paging/sharing more completely
and apologize, Andres, if I have cast aspersions about its/your
implementation, I was simply trying to use it as another
example of an in-hypervisor page allocation that is not
directly under the control of the toolstack. I do understand
and agree that IF the toolstack is capable of intelligently
managing d->max_pages across all domains, then your model
for handling CoW hits will be sufficient.
So... again... peace?
Dan
next prev parent reply other threads:[~2013-01-03 18:49 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18000.1354568068.1399.xen-devel@lists.xen.org>
2012-12-04 3:24 ` Proposed XENMEM_claim_pages hypercall: Analysis of problem and alternate solutions Andres Lagar-Cavilla
2012-12-18 22:17 ` Konrad Rzeszutek Wilk
2012-12-19 12:53 ` George Dunlap
2012-12-19 13:48 ` George Dunlap
2013-01-03 20:38 ` Dan Magenheimer
2013-01-02 21:59 ` Konrad Rzeszutek Wilk
2013-01-14 18:28 ` George Dunlap
2013-01-22 21:57 ` Konrad Rzeszutek Wilk
2013-01-23 18:36 ` Dave Scott
2013-02-12 15:38 ` Konrad Rzeszutek Wilk
2012-12-20 16:04 ` Tim Deegan
2013-01-02 15:31 ` Andres Lagar-Cavilla
2013-01-02 21:43 ` Dan Magenheimer
2013-01-03 16:25 ` Andres Lagar-Cavilla
2013-01-03 18:49 ` Dan Magenheimer [this message]
2013-01-07 14:43 ` Ian Campbell
2013-01-07 18:41 ` Dan Magenheimer
2013-01-08 9:03 ` Ian Campbell
2013-01-08 19:41 ` Dan Magenheimer
2013-01-09 10:41 ` Ian Campbell
2013-01-09 14:44 ` Dan Magenheimer
2013-01-09 14:58 ` Ian Campbell
2013-01-14 15:45 ` George Dunlap
2013-01-14 18:18 ` Dan Magenheimer
2013-01-14 19:42 ` George Dunlap
2013-01-14 23:14 ` Dan Magenheimer
2013-01-23 12:18 ` Ian Campbell
2013-01-23 17:34 ` Dan Magenheimer
2013-02-12 16:18 ` Konrad Rzeszutek Wilk
2013-01-10 10:31 ` Ian Campbell
2013-01-10 18:42 ` Dan Magenheimer
2013-01-02 21:38 ` Dan Magenheimer
2013-01-03 16:24 ` Andres Lagar-Cavilla
2013-01-03 18:33 ` Dan Magenheimer
2013-01-10 17:13 ` Tim Deegan
2013-01-10 21:43 ` Dan Magenheimer
2013-01-17 15:12 ` Tim Deegan
2013-01-17 15:26 ` Andres Lagar-Cavilla
2013-01-22 19:22 ` Dan Magenheimer
2013-01-23 12:18 ` Ian Campbell
2013-01-23 16:05 ` Dan Magenheimer
2013-01-02 15:29 ` Andres Lagar-Cavilla
2013-01-11 16:03 ` Konrad Rzeszutek Wilk
2013-01-11 16:13 ` Andres Lagar-Cavilla
2013-01-11 19:08 ` Konrad Rzeszutek Wilk
2013-01-14 16:00 ` George Dunlap
2013-01-14 16:11 ` Andres Lagar-Cavilla
2013-01-17 15:16 ` Tim Deegan
2013-01-18 21:45 ` Konrad Rzeszutek Wilk
2013-01-21 10:29 ` Tim Deegan
2013-02-12 15:54 ` Konrad Rzeszutek Wilk
2013-02-14 13:32 ` Konrad Rzeszutek Wilk
2012-12-03 20:54 Dan Magenheimer
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=d6b1ecdd-0a6c-4059-bfdf-a32ffb55e8da@default \
--to=dan.magenheimer@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andreslc@gridcentric.ca \
--cc=ian.campbell@citrix.com \
--cc=keir@xen.org \
--cc=konrad@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).