From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86: fix memory cut-off when using PFN compression
Date: Wed, 11 Sep 2013 16:23:32 +0200 [thread overview]
Message-ID: <1378909412.2821.120.camel@Solace> (raw)
In-Reply-To: <523096FC02000078000F27BD@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 841 bytes --]
On mer, 2013-09-11 at 15:14 +0100, Jan Beulich wrote:
> >>> On 11.09.13 at 16:02, Dario Faggioli <dario.faggioli@citrix.com> wrote:
>
> > I tried to find that out by myself and I'd say that is not the case
> > (i.e., amount of free memory is not affected), as I did not fine any
> > call to node_spanned_pages()... Did I miss anything?
>
> No, this indeed is only about the node size, not a node's free
> memory.
>
Fine, then, from that point of view (and for what it's worth):
Acked-by: Dario Faggioli <dario.faggioli@citrix.com>
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-09-11 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 12:48 [PATCH] x86: fix memory cut-off when using PFN compression Jan Beulich
2013-09-11 14:02 ` Dario Faggioli
2013-09-11 14:14 ` Jan Beulich
2013-09-11 14:23 ` Dario Faggioli [this message]
2013-09-11 14:04 ` Keir Fraser
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=1378909412.2821.120.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.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 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).