From: David Vrabel <david.vrabel@citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Konrad Wilk <konrad.wilk@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH v2] xen: Fix selfballooning and ensure it doesn't go too far
Date: Tue, 27 Sep 2011 18:08:38 +0100 [thread overview]
Message-ID: <4E820316.6070101@citrix.com> (raw)
In-Reply-To: <f42e2a83-15f6-4767-a7df-8a23ceac239e@default>
On 27/09/11 17:19, Dan Magenheimer wrote:
>> From: David Vrabel [mailto:david.vrabel@citrix.com]
>> Subject: Re: [PATCH v2] xen: Fix selfballooning and ensure it doesn't go too far
>>
>> On 27/09/11 16:03, Dan Magenheimer wrote:
>>> Note: This patch is also now in a git tree at:
>>>
>>> git://oss.oracle.com/git/djm/tmem.git#selfballoon-fix-v2
>>>
>>> The balloon driver's "current_pages" is very different from
>>> totalram_pages. Self-ballooning needs to be driven by
>>> the latter.
>
> Hi David --
>
> Thanks for the feedback!
>
>> I don't think this part of the change makes any difference. It looks like it
>> rearranges the maths without changing the end result (other than
>> slightly increasing the rate of change).
>> I think this (partial, untested) patch is equivalent:
>
> Actually it does.
Really?
Both patched and unpatched the new target, S, is (eventually):
S = V + F + C - T
where V is vm_committed_as, F is frontswap_curr_pages(), C is
balloon_stats.current_pages, and T = totalram_pages.
Perhaps the refactoring of the maths is a good idea (I don't think so)
but it shouldn't be part of this patch and it shouldn't be described as
a fix.
David
next prev parent reply other threads:[~2011-09-27 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 15:03 Dan Magenheimer
2011-09-27 15:57 ` David Vrabel
2011-09-27 16:19 ` Dan Magenheimer
2011-09-27 17:08 ` David Vrabel [this message]
2011-09-27 20:25 ` 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=4E820316.6070101@citrix.com \
--to=david.vrabel@citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®