linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pavan Kondeti <quic_pkondeti@quicinc.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pavankumar Kondeti <quic_pkondeti@quicinc.com>,
	<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Minchan Kim <minchan@kernel.org>,
	Charan Teja Kalla <quic_charante@quicinc.com>,
	Prakash Gupta <quic_guptap@quicinc.com>,
	Divyanand Rangu <quic_drangu@quicinc.com>
Subject: Re: [PATCH] mm/madvise: fix madvise_pageout for private file mappings
Date: Thu, 1 Dec 2022 08:30:45 +0530	[thread overview]
Message-ID: <20221201030045.GB3980@hu-pkondeti-hyd.qualcomm.com> (raw)
In-Reply-To: <20221130151739.a7771037aa83ff536ac2edd5@linux-foundation.org>

On Wed, Nov 30, 2022 at 03:17:39PM -0800, Andrew Morton wrote:
> 
> On Wed, 9 Nov 2022 10:48:36 +0530 Pavankumar Kondeti <quic_pkondeti@quicinc.com> wrote:
> 
> > When MADV_PAGEOUT is called on a private file mapping VMA region,
> > we bail out early if the process is neither owner nor write capable
> > of the file. However, this VMA may have both private/shared clean
> > pages and private dirty pages. The opportunity of paging out the
> > private dirty pages (Anon pages) is missed. Fix this by caching
> > the file access check and use it later along with PageAnon() during
> > page walk.
> > 
> > We observe ~10% improvement in zram usage, thus leaving more available
> > memory on a 4GB RAM system running Android.
> > 
> 
> Could we please have some reviewer input on this?
> 
> Thanks.
> 

Thanks Andrew for the reminder. Fyi, this patch has been included in Android
Generic Kernel Image (5.10 and 5.15 kernels) as we have seen good savings on
Android. It would make a difference on a low memory android devices.

Suren/Minchan,

Can you please do the needful?

Thanks,
Pavan


  reply	other threads:[~2022-12-01  3:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  5:18 Pavankumar Kondeti
2022-11-30 23:17 ` Andrew Morton
2022-12-01  3:00   ` Pavan Kondeti [this message]
2022-12-01 19:51     ` Suren Baghdasaryan
2022-12-01 13:01 ` David Hildenbrand
2022-12-01 13:36   ` Pavan Kondeti
2022-12-01 13:46 ` Mark Hemment
2022-12-01 14:17   ` 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=20221201030045.GB3980@hu-pkondeti-hyd.qualcomm.com \
    --to=quic_pkondeti@quicinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=quic_charante@quicinc.com \
    --cc=quic_drangu@quicinc.com \
    --cc=quic_guptap@quicinc.com \
    --cc=surenb@google.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