From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, shli@kernel.org
Subject: Re: [PATCH] mm/swap: Use page flags to determine LRU list in __activate_page()
Date: Fri, 27 Oct 2017 09:36:37 +0530 [thread overview]
Message-ID: <2fc28494-d0d2-9b65-aeb7-1ccabf210917@linux.vnet.ibm.com> (raw)
In-Reply-To: <d01827c0-8858-5688-dc16-1e2f597ec55c@linux.vnet.ibm.com>
On 10/23/2017 08:52 AM, Anshuman Khandual wrote:
> On 10/19/2017 09:03 PM, Michal Hocko wrote:
>> On Thu 19-10-17 20:26:57, Anshuman Khandual wrote:
>>> Its already assumed that the PageActive flag is clear on the input
>>> page, hence page_lru(page) will pick the base LRU for the page. In
>>> the same way page_lru(page) will pick active base LRU, once the
>>> flag PageActive is set on the page. This change of LRU list should
>>> happen implicitly through the page flags instead of being hard
>>> coded.
>>
>> The patch description tells what but it doesn't explain _why_? Does the
>> resulting code is better, more optimized or is this a pure readability
>> thing?
>
> Not really. Not only it removes couple of lines of code but it also
> makes it look more logical from function flow point of view as well.
>
>>
>> All I can see is that page_lru is more complex and a large part of it
>> can be optimized away which has been done manually here. I suspect the
>> compiler can deduce the same thing.
>
> Why not ? I mean, that is the essence of the function page_lru() which
> should get us the exact LRU list the page should be on and hence we
> should not hand craft these manually.
Hi Michal,
Did not hear from you on this. So wondering what is the verdict
about this patch ?
- Anshuman
next prev parent reply other threads:[~2017-10-27 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 14:56 [PATCH] mm/swap: Use page flags to determine LRU list in __activate_page() Anshuman Khandual
2017-10-19 15:33 ` Michal Hocko
2017-10-23 3:22 ` Anshuman Khandual
2017-10-27 4:06 ` Anshuman Khandual [this message]
2017-10-27 7:57 ` Michal Hocko
2017-10-31 12:45 ` Vlastimil Babka
2017-11-02 11:44 ` Anshuman Khandual
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=2fc28494-d0d2-9b65-aeb7-1ccabf210917@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shli@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).