From: Rik van Riel <riel@redhat.com>
To: Hugh Dickins <hughd@google.com>,
Ebru Akagunduz <ebru.akagunduz@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
kirill.shutemov@linux.intel.com, n-horiguchi@ah.jp.nec.com,
aarcange@redhat.com, iamjoonsoo.kim@lge.com, xiexiuqi@huawei.com,
gorcunov@openvz.org, linux-kernel@vger.kernel.org,
mgorman@suse.de, rientjes@google.com, vbabka@suse.cz,
aneesh.kumar@linux.vnet.ibm.com, hannes@cmpxchg.org,
mhocko@suse.cz, boaz@plexistor.com, raindel@mellanox.com
Subject: Re: [RFC v5 0/3] mm: make swapin readahead to gain more thp performance
Date: Fri, 26 Feb 2016 09:51:56 -0500 [thread overview]
Message-ID: <1456498316.25322.35.camel@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1602252151030.9793@eggly.anvils>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Thu, 2016-02-25 at 22:17 -0800, Hugh Dickins wrote:
> On Fri, 26 Feb 2016, Ebru Akagunduz wrote:
> > in Thu, Feb 25, 2016 at 05:35:50PM -0500, Rik van Riel wrote:
>
> > > Am I forgetting anything obvious?
> > >
> > > Is this too aggressive?
> > >
> > > Not aggressive enough?
> > >
> > > Could PGPGOUT + PGSWPOUT be a useful
> > > in-between between just PGSWPOUT or
> > > PGSTEAL_*?
>
> I've no idea offhand, would have to study what each of those
> actually means: I'm really not familiar with them myself.
There are a few levels of page reclaim activity:
PGSTEAL_* - any page was reclaimed, this could just
be file pages for streaming file IO,etc
PGPGOUT - the VM wrote pages back to disk to reclaim
them, this could include file pages
PGSWPOUT - the VM wrote something to swap to reclaim
memory
I am not sure which level of aggressiveness khugepaged
should check against, but my gut instinct would probably
be the second or third.
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-26 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 19:31 [RFC v5 0/3] mm: make swapin readahead to gain more thp performance Ebru Akagunduz
2015-09-14 19:31 ` [RFC v5 1/3] mm: add tracepoint for scanning pages Ebru Akagunduz
2015-09-14 19:31 ` [RFC v5 2/3] mm: make optimistic check for swapin readahead Ebru Akagunduz
2015-09-14 19:47 ` Rik van Riel
2015-09-14 21:33 ` Andrew Morton
2015-09-15 20:08 ` Ebru Akagunduz
2015-09-14 19:31 ` [RFC v5 3/3] mm: make swapin readahead to improve thp collapse rate Ebru Akagunduz
2015-09-17 13:28 ` Kirill A. Shutemov
2015-09-17 15:13 ` Kirill A. Shutemov
2015-09-14 21:41 ` [RFC v5 0/3] mm: make swapin readahead to gain more thp performance Andrew Morton
2016-02-25 7:36 ` Hugh Dickins
2016-02-25 22:35 ` Rik van Riel
2016-02-25 23:30 ` Ebru Akagunduz
2016-02-26 6:17 ` Hugh Dickins
2016-02-26 14:51 ` Rik van Riel [this message]
2016-03-03 22:08 ` Ebru Akagunduz
2016-02-25 23:16 ` Ebru Akagunduz
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=1456498316.25322.35.camel@redhat.com \
--to=riel@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=boaz@plexistor.com \
--cc=ebru.akagunduz@gmail.com \
--cc=gorcunov@openvz.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=raindel@mellanox.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=xiexiuqi@huawei.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;
as well as URLs for NNTP newsgroup(s).