From: Vlastimil Babka <vbabka@suse.cz>
To: Wei Yang <richard.weiyang@gmail.com>,
willy@infradead.org, mhocko@suse.com,
mgorman@techsingularity.net
Cc: linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: [RFC] put page to pcp->lists[] tail if it is not on the same node
Date: Fri, 19 Oct 2018 15:43:29 +0200 [thread overview]
Message-ID: <36be02a3-cdb9-15d0-a491-eba34675db3b@suse.cz> (raw)
In-Reply-To: <20181019043303.s5axhjfb2v2lzsr3@master>
On 10/19/18 6:33 AM, Wei Yang wrote:
> @@ -2763,7 +2764,14 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn)
> }
>
> pcp = &this_cpu_ptr(zone->pageset)->pcp;
> - list_add(&page->lru, &pcp->lists[migratetype]);
My impression is that you think there's only one pcp per cpu. But the
"pcp" here is already specific to the zone (and thus node) of the page
being freed. So it doesn't matter if we put the page to the list or
tail. For allocation we already typically prefer local nodes, thus local
zones, thus pcp's containing only local pages.
> + /*
> + * If the page has the same node_id as this cpu, put the page at head.
> + * Otherwise, put at the end.
> + */
> + if (page_node == pcp->node)
So this should in fact be always true due to what I explained above.
Otherwise I second the recommendation from Mel.
Cheers,
Vlastimil
next prev parent reply other threads:[~2018-10-19 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 4:33 Wei Yang
2018-10-19 8:38 ` Mel Gorman
2018-10-20 0:54 ` Wei Yang
2018-10-20 16:33 ` Wei Yang
2018-10-21 2:36 ` Wei Yang
2018-10-21 12:12 ` Mel Gorman
2018-10-22 1:24 ` Wei Yang
2018-10-19 13:43 ` Vlastimil Babka [this message]
2018-10-20 1:38 ` Wei Yang
2018-10-20 16:10 ` Wei Yang
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=36be02a3-cdb9-15d0-a491-eba34675db3b@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=richard.weiyang@gmail.com \
--cc=willy@infradead.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