From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <hannes@cmpxchg.org>, <minchan@kernel.org>,
<quic_pkondeti@quicinc.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: madvise: fix uneven accounting of psi
Date: Thu, 1 Jun 2023 18:48:57 +0530 [thread overview]
Message-ID: <bad9f1e3-bbf5-7fa6-946c-55bccb70ec65@quicinc.com> (raw)
In-Reply-To: <20230531150449.56311ca2ea6184b413517672@linux-foundation.org>
Thanks Andrew!!
On 6/1/2023 3:34 AM, Andrew Morton wrote:
>> This patch is tested on Android, Snapdragon SoC with 8Gb RAM, 4GB swap
>> mounted on zram which has 2GB of backingdev. The test case involved
>> launching some memory hungry apps in an order and do the proactive
>> reclaim for the app that went to background using madvise(MADV_PAGEOUT).
>> We are seeing ~40% less total values of psi mem some and full when this
>> patch is combined with [1].
> Does this accounting inaccuracy have any perceptible runtime effects?
>
With the testcase mentioned, we are able to achieve better app
concurrency(It is a measure on Android of how many apps that can survive
by not getting killed by lmkd(which relies on PSI events to take the
decissions) by the end of the testcase).
The total memsome and memfull psi events(measured in usec) are as below:
mem PSI w/o patch with patch
some 61255313 21867736
full 31353138 15391454
Thanks,
Charan
>
next prev parent reply other threads:[~2023-06-01 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:09 Charan Teja Kalla
2023-05-31 22:04 ` Andrew Morton
2023-06-01 13:18 ` Charan Teja Kalla [this message]
2023-05-31 22:19 ` Johannes Weiner
2023-06-01 13:07 ` Charan Teja Kalla
2023-06-05 18:00 ` Johannes Weiner
2023-06-06 14:53 ` Charan Teja Kalla
2023-06-06 19:48 ` Suren Baghdasaryan
2023-06-09 12:42 ` Charan Teja Kalla
2023-06-09 23:13 ` Suren Baghdasaryan
2023-06-12 13:40 ` Johannes Weiner
2023-06-26 14:31 ` Charan Teja Kalla
2023-06-27 22:50 ` Suren Baghdasaryan
2023-06-13 3:13 ` Pavan Kondeti
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=bad9f1e3-bbf5-7fa6-946c-55bccb70ec65@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=quic_pkondeti@quicinc.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®