From: Vlastimil Babka <vbabka@suse.cz>
To: Rik van Riel <riel@redhat.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
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,
aneesh.kumar@linux.vnet.ibm.com, hughd@google.com,
hannes@cmpxchg.org, mhocko@suse.cz, boaz@plexistor.com,
raindel@mellanox.com
Subject: Re: [RFC v2 3/3] mm: make swapin readahead to improve thp collapse rate
Date: Wed, 24 Jun 2015 14:33:02 +0200 [thread overview]
Message-ID: <558AA37E.20106@suse.cz> (raw)
In-Reply-To: <558766E4.5020801@redhat.com>
On 06/22/2015 03:37 AM, Rik van Riel wrote:
> On 06/21/2015 02:11 PM, Kirill A. Shutemov wrote:
>> On Sat, Jun 20, 2015 at 02:28:06PM +0300, Ebru Akagunduz wrote:
>>> + __collapse_huge_page_swapin(mm, vma, address, pmd, pte);
>>> +
>>
>> And now the pages we swapped in are not isolated, right?
>> What prevents them from being swapped out again or whatever?
>
> Nothing, but __collapse_huge_page_isolate is run with the
> appropriate locks to ensure that once we actually collapse
> the THP, things are present.
>
> The way do_swap_page is called, khugepaged does not even
> wait for pages to be brought in from swap. It just maps
> in pages that are in the swap cache, and which can be
> immediately locked (without waiting).
>
> It will also start IO on pages that are not in memory
> yet, and will hopefully get those next round.
Hm so what if the process is slightly larger than available memory and really
doesn't touch the swapped out pages that much? Won't that just be thrashing and
next round you find them swapped out again?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-06-24 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 11:28 [RFC v2 0/3] mm: make swapin readahead to gain more thp performance Ebru Akagunduz
2015-06-20 11:28 ` [RFC v2 1/3] mm: add tracepoint for scanning pages Ebru Akagunduz
2015-06-21 17:42 ` Kirill A. Shutemov
2015-06-24 11:59 ` Vlastimil Babka
2015-06-20 11:28 ` [RFC v2 2/3] mm: make optimistic check for swapin readahead Ebru Akagunduz
2015-06-21 17:55 ` Kirill A. Shutemov
2015-06-20 11:28 ` [RFC v2 3/3] mm: make swapin readahead to improve thp collapse rate Ebru Akagunduz
2015-06-21 18:11 ` Kirill A. Shutemov
2015-06-21 19:19 ` Kirill A. Shutemov
2015-06-22 1:37 ` Rik van Riel
2015-06-24 12:33 ` Vlastimil Babka [this message]
2015-06-26 1:44 ` Rik van Riel
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=558AA37E.20106@suse.cz \
--to=vbabka@suse.cz \
--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=kirill@shutemov.name \
--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=riel@redhat.com \
--cc=rientjes@google.com \
--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).