From: Aaron Lu <aaron.lu@intel.com>
To: "Chen, Tim C" <tim.c.chen@intel.com>, Linux MM <linux-mm@kvack.org>
Cc: "Huang, Ying" <ying.huang@intel.com>
Subject: Re: [RFC PATCH] swap: choose swap device according to numa node
Date: Tue, 3 May 2016 17:14:29 +0800 [thread overview]
Message-ID: <dffa3c90-1b2d-b63e-abd1-b6b959fe23db@intel.com> (raw)
In-Reply-To: <045D8A5597B93E4EBEDDCBF1FC15F509359EAF8F@fmsmsx104.amr.corp.intel.com>
On 04/30/2016 04:25 AM, Chen, Tim C wrote:
> Wonder if choosing the swap device by numa node is the most
> effective way to spread the pages among the swap devices.
The intent of this patch is not to spread the pages among the swap
devices(thus to reduce lock contention on swap device's radix tree),
it's about speed up the IOs :-)
> The speedup comes from spreading the swap activities among
> equal priority swap devices to reduce contention on swap devices.
For v4.5, yes. And for this patch, it also has speed ups by doing IOs
locally.
> If the activities are mostly confined to 1 node, then we still could
> have contention on a device.
Indeed, but I suppose that would normally happen if people has played
with numactl themselves? Otherwise, the scheduler would probably spread
the threads evenly.
Ying suggests we use a config for people to turn this off in his reply
and I can of course add that.
> An alternative may be we pick another swap device on each
> pass of shrink_page_list to try to swap pages.
This can be achieved by setting the two swap devices with equal priority
and then the two swap devices will be used round robin. I have already
used it as a comparing config:
throughput of v4.5(swap device with equal priority)
Thanks for the comments!
--
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:[~2016-05-03 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 8:34 Aaron Lu
2016-04-29 20:25 ` Chen, Tim C
2016-05-03 9:14 ` Aaron Lu [this message]
2016-07-05 3:19 ` [RFC RESEND " Aaron Lu
2016-07-05 5:57 ` Yu Chen
2016-07-05 6:22 ` Aaron Lu
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=dffa3c90-1b2d-b63e-abd1-b6b959fe23db@intel.com \
--to=aaron.lu@intel.com \
--cc=linux-mm@kvack.org \
--cc=tim.c.chen@intel.com \
--cc=ying.huang@intel.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