All of lore.kernel.org
 help / color / mirror / Atom feed
From: vjitta@codeaurora.org
To: Laura Abbott <labbott@redhat.com>
Cc: devel@driverdev.osuosl.org, linux-kernel-owner@vger.kernel.org,
	tkjos@android.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, arve@android.com, maco@android.com,
	sumit.semwal@linaro.org
Subject: Re: [PATCH] ion: Consider ion pool pages as indirectly reclaimable
Date: Fri, 27 Apr 2018 10:40:36 +0530	[thread overview]
Message-ID: <fb3f0974e9e83b33e7eac267aeecf130@codeaurora.org> (raw)
In-Reply-To: <8618859b-06f9-39a7-80a9-af36cf9faf9f@redhat.com>

On 2018-04-25 21:17, Laura Abbott wrote:
> On 04/24/2018 08:43 PM, vjitta@codeaurora.org wrote:
>> From: Vijayanand Jitta <vjitta@codeaurora.org>
>> 
>> An issue is observed where mallocs are failing due to overcommit 
>> failure.
>> The failure happens when there is high ION page pool since ION page
>> pool is not considered reclaimable by the overcommit calculation code.
>> This change considers ion pool pages as indirectly reclaimable and 
>> thus
>> accounted as available memory in the overcommit calculation.
>> 
>> Signed-off-by: Vijayanand Jitta <vjitta@codeaurora.org>
>> ---
>>   drivers/staging/android/ion/ion_page_pool.c | 5 +++++
>>   1 file changed, 5 insertions(+)
>> 
>> diff --git a/drivers/staging/android/ion/ion_page_pool.c 
>> b/drivers/staging/android/ion/ion_page_pool.c
>> index db8f614..9bc56eb 100644
>> --- a/drivers/staging/android/ion/ion_page_pool.c
>> +++ b/drivers/staging/android/ion/ion_page_pool.c
>> @@ -32,6 +32,9 @@ static void ion_page_pool_add(struct ion_page_pool 
>> *pool, struct page *page)
>>   		list_add_tail(&page->lru, &pool->low_items);
>>   		pool->low_count++;
>>   	}
>> +
>> +	mod_node_page_state(page_pgdat(page), 
>> NR_INDIRECTLY_RECLAIMABLE_BYTES,
>> +			    (1 << (PAGE_SHIFT + pool->order)));
>>   	mutex_unlock(&pool->mutex);
>>   }
>>   @@ -50,6 +53,8 @@ static struct page *ion_page_pool_remove(struct 
>> ion_page_pool *pool, bool high)
>>   	}
>>     	list_del(&page->lru);
>> +	mod_node_page_state(page_pgdat(page), 
>> NR_INDIRECTLY_RECLAIMABLE_BYTES,
>> +			    -(1 << (PAGE_SHIFT + pool->order)));
>>   	return page;
>>   }
>> 
> 
> I'm sure this fixes the problem but I don't think we want to
> start throwing page adjustments into Ion. Why isn't this
> memory already considered reclaimable by existing calculations?
> 
> Thanks,
> Laura

You can refer to discussion here https://lkml.org/lkml/2018/3/5/361 
introducing
NR_INDIRECTLY_RECLAIMABLE_BYTES for the memory which is not currently 
considered
as reclaimable

Thanks,
Vijay
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2018-04-27  5:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25  3:43 [PATCH] ion: Consider ion pool pages as indirectly reclaimable vjitta
2018-04-25 15:47 ` Laura Abbott
2018-04-27  5:10   ` vjitta [this message]
2018-04-27  9:29     ` vjitta
2018-04-27 21:30       ` Laura Abbott

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=fb3f0974e9e83b33e7eac267aeecf130@codeaurora.org \
    --to=vjitta@codeaurora.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=sumit.semwal@linaro.org \
    --cc=tkjos@android.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.