From: "Huang\, Ying" <ying.huang@intel.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead
Date: Mon, 26 Feb 2018 13:18:50 +0800 [thread overview]
Message-ID: <87d10stjk5.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20180226045617.GA112402@rodete-desktop-imager.corp.google.com> (Minchan Kim's message of "Mon, 26 Feb 2018 13:56:17 +0900")
Minchan Kim <minchan@kernel.org> writes:
> On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote:
>> <minchan@kernel.org> writes:
>> [snip]
>>
>> > diff --git a/mm/swap_state.c b/mm/swap_state.c
>> > index 39ae7cfad90f..c56cce64b2c3 100644
>> > --- a/mm/swap_state.c
>> > +++ b/mm/swap_state.c
>> > @@ -332,32 +332,38 @@ struct page *lookup_swap_cache(swp_entry_t entry, struct vm_area_struct *vma,
>> > unsigned long addr)
>> > {
>> > struct page *page;
>> > - unsigned long ra_info;
>> > - int win, hits, readahead;
>> >
>> > page = find_get_page(swap_address_space(entry), swp_offset(entry));
>> >
>> > INC_CACHE_INFO(find_total);
>> > if (page) {
>> > + bool vma_ra = swap_use_vma_readahead();
>> > + bool readahead = TestClearPageReadahead(page);
>> > +
>>
>> TestClearPageReadahead() cannot be called for compound page. As in
>>
>> PAGEFLAG(Readahead, reclaim, PF_NO_COMPOUND)
>> TESTCLEARFLAG(Readahead, reclaim, PF_NO_COMPOUND)
>>
>> > INC_CACHE_INFO(find_success);
>> > if (unlikely(PageTransCompound(page)))
>> > return page;
>> > - readahead = TestClearPageReadahead(page);
>>
>> So we can only call it here after checking whether page is compound.
>
> Hi Huang,
>
> Thanks for cathing this.
> However, I don't see the reason we should rule out THP page for
> readahead marker. Could't we relax the rule?
>
> I hope we can do so that we could remove PageTransCompound check
> for readahead marker, which makes code ugly.
>
> From 748b084d5c3960ec2418d8c51a678aada30f1072 Mon Sep 17 00:00:00 2001
> From: Minchan Kim <minchan@kernel.org>
> Date: Mon, 26 Feb 2018 13:46:43 +0900
> Subject: [PATCH] mm: relax policy for PG_readahead
>
> This flag is in use for anon THP page so let's relax it.
>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
> ---
> include/linux/page-flags.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
> index e34a27727b9a..f12d4dfae580 100644
> --- a/include/linux/page-flags.h
> +++ b/include/linux/page-flags.h
> @@ -318,8 +318,8 @@ PAGEFLAG(MappedToDisk, mappedtodisk, PF_NO_TAIL)
> /* PG_readahead is only used for reads; PG_reclaim is only for writes */
> PAGEFLAG(Reclaim, reclaim, PF_NO_TAIL)
> TESTCLEARFLAG(Reclaim, reclaim, PF_NO_TAIL)
> -PAGEFLAG(Readahead, reclaim, PF_NO_COMPOUND)
> - TESTCLEARFLAG(Readahead, reclaim, PF_NO_COMPOUND)
> +PAGEFLAG(Readahead, reclaim, PF_NO_TAIL)
> + TESTCLEARFLAG(Readahead, reclaim, PF_NO_TAIL)
>
> #ifdef CONFIG_HIGHMEM
> /*
We never set Readahead bit for THP in reality. The original code acts
as document for this. I don't think it is a good idea to change this
without a good reason.
Best Regards,
Huang, Ying
--
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:[~2018-02-26 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 8:52 [PATCH RESEND 0/2] swap readahead clean up minchan
2018-02-20 8:52 ` [PATCH RESEND 1/2] mm: swap: clean up swap readahead minchan
2018-02-23 8:02 ` Huang, Ying
2018-02-26 4:56 ` Minchan Kim
2018-02-26 5:18 ` Huang, Ying [this message]
2018-02-26 5:41 ` Minchan Kim
2018-02-26 8:22 ` Huang, Ying
2018-02-20 8:52 ` [PATCH RESEND 2/2] mm: swap: unify cluster-based and vma-based " minchan
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=87d10stjk5.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
/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).