From: Wei Yang <richard.weiyang@gmail.com>
To: willy@infradead.org, mhocko@suse.com, mgorman@techsingularity.net
Cc: richard.weiyang@gmail.com, linux-mm@kvack.org, akpm@linux-foundation.org
Subject: [RFC] put page to pcp->lists[] tail if it is not on the same node
Date: Fri, 19 Oct 2018 04:33:03 +0000 [thread overview]
Message-ID: <20181019043303.s5axhjfb2v2lzsr3@master> (raw)
node
Reply-To: Wei Yang <richard.weiyang@gmail.com>
Masters,
During the code reading, I pop up this idea.
In case we put some intelegence of NUMA node to pcp->lists[], we may
get a better performance.
The idea is simple:
Put page on other nodes to the tail of pcp->lists[], because we
allocate from head and free from tail.
Since my desktop just has one numa node, I couldn't test the effect. I
just run a kernel build test to see if it would degrade current kernel.
The result looks not bad.
make -j4 bzImage
base-line:
real 6m15.947s
user 21m14.481s
sys 2m34.407s
real 6m16.089s
user 21m18.295s
sys 2m35.551s
real 6m16.239s
user 21m17.590s
sys 2m35.252s
patched:
real 6m14.558s
user 21m18.374s
sys 2m33.143s
real 6m14.606s
user 21m14.969s
sys 2m32.039s
real 6m15.264s
user 21m16.698s
sys 2m33.024s
Sorry for sending this without a real justification. Hope this will not
make you uncomfortable. I would be very glad if you suggest some
verifications that I could do.
Below is my testing patch, look forward your comments.
next reply other threads:[~2018-10-19 4:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 4:33 Wei Yang [this message]
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
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=20181019043303.s5axhjfb2v2lzsr3@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.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