From: "Andres Lagar-Cavilla" <andres@lagarcavilla.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: dan.magenheimer@oracle.com, ian.campbell@citrix.com,
andres@gridcentric.ca, tim@xen.org,
xen-devel <xen-devel@lists.xen.org>,
ian.jackson@citrix.com, adin@gridcentric.ca
Subject: Re: [PATCH] Low mem virq incremental adjustments
Date: Wed, 7 Mar 2012 10:12:19 -0800 [thread overview]
Message-ID: <dfd9168bfe356e433fb3687f228f569e.squirrel@webmail.lagarcavilla.org> (raw)
In-Reply-To: <4F57A2C40200007800076F24@nat28.tlf.novell.com>
> >>> On 07.03.12 at 17:15, Andres Lagar-Cavilla <andres@lagarcavilla.org>
> wrote:
>> --- a/xen/common/page_alloc.c
>> +++ b/xen/common/page_alloc.c
>> @@ -377,7 +377,10 @@ static void __init setup_low_mem_virq(vo
>>
>> static void check_low_mem_virq(void)
>> {
>> - if ( unlikely(total_avail_pages <= low_mem_virq_th) )
>> + unsigned long avail_pages = total_avail_pages +
>> + (opt_tmem) ? tmem_freeable_pages(): 0;
>
> Can tmem_freeable_pages() return anything other than zero when
> opt_tmem is zero? (I.e. is the [improperly parenthesized!] conditional
> expression necessary at all?)
I'm not sure. I'll let Dan take it from here, as he surely knows the right
way. He acked it the way it is.
Andres
>
> Jan
>
>> +
>> + if ( unlikely(avail_pages <= low_mem_virq_th) )
>> {
>> send_global_virq(VIRQ_ENOMEM);
>>
>> @@ -391,7 +394,7 @@ static void check_low_mem_virq(void)
>> return;
>> }
>>
>> - if ( unlikely(total_avail_pages >= low_mem_virq_high) )
>> + if ( unlikely(avail_pages >= low_mem_virq_high) )
>> {
>> /* Reset hysteresis. Bring threshold up one order.
>> * If we are back where originally set, set high
>
>
>
>
next prev parent reply other threads:[~2012-03-07 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 16:15 [PATCH] Low mem virq incremental adjustments Andres Lagar-Cavilla
2012-03-07 17:02 ` Jan Beulich
2012-03-07 18:12 ` Andres Lagar-Cavilla [this message]
2012-03-08 21:59 ` Dan Magenheimer
2012-03-09 9:04 ` Jan Beulich
2012-03-09 9:56 ` 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=dfd9168bfe356e433fb3687f228f569e.squirrel@webmail.lagarcavilla.org \
--to=andres@lagarcavilla.org \
--cc=JBeulich@suse.com \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=dan.magenheimer@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--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 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.