From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
Bob Liu <bob.liu@oracle.com>,
keir.xen@gmail.com, Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] xen/tmem: Don't use map_domain_page for long-life-time pages.
Date: Thu, 13 Jun 2013 14:56:41 +0100 [thread overview]
Message-ID: <51B9CF99.6000407@eu.citrix.com> (raw)
In-Reply-To: <1371131752.24512.541.camel@zakaz.uk.xensource.com>
On 13/06/13 14:55, Ian Campbell wrote:
> On Thu, 2013-06-13 at 14:49 +0100, Jan Beulich wrote:
>>>>> On 13.06.13 at 15:24, George Dunlap <george.dunlap@eu.citrix.com> wrote:
>>> Did I understand correctly that the map_domain_page() was required on
>>> >5TiB systems, presumably because of limited virtual address space? In
>>> which case this code will fail on those systems?
>>>
>>> If that is the case, then we need to have a way to make sure tmem cannot
>>> be enabled on such systems.
>> Tmem is full of assumptions that all memory is mapped, and hence
>> one of the requirements here was to disable tmem when that
>> assumption is not true (until eventually tmem would get fixed).
> Isn't this change moving it further away from that fixed state though?
Perhaps, but it's probably the best change for 4.3 at this point.
-George
next prev parent reply other threads:[~2013-06-13 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 12:50 [PATCH] xen/tmem: Don't use map_domain_page for long-life-time pages Konrad Rzeszutek Wilk
2013-06-13 13:24 ` George Dunlap
2013-06-13 13:29 ` Konrad Rzeszutek Wilk
2013-08-22 10:15 ` Josh Zhao
2013-08-22 10:27 ` Ian Campbell
2013-08-22 10:28 ` Josh Zhao
2013-06-13 13:40 ` Ian Campbell
2013-06-13 13:49 ` Jan Beulich
2013-06-13 13:55 ` Ian Campbell
2013-06-13 13:56 ` George Dunlap [this message]
2013-06-13 14:04 ` Jan Beulich
2013-06-13 14:10 ` Ian Campbell
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=51B9CF99.6000407@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=bob.liu@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=xen-devel@lists.xensource.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.