From: "ying.huang@intel.com" <ying.huang@intel.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Yang Shi <shy828301@gmail.com>, Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: swap: determine swap device by using page nid
Date: Fri, 22 Apr 2022 14:27:45 +0800 [thread overview]
Message-ID: <4f1bc4dc65117a185833555ff8df30a944453499.camel@intel.com> (raw)
In-Reply-To: <YmJKBaq1yj6/iBJ3@ziqianlu-desk1>
On Fri, 2022-04-22 at 14:24 +0800, Aaron Lu wrote:
> On Thu, Apr 21, 2022 at 04:34:09PM +0800, ying.huang@intel.com wrote:
> > On Thu, 2022-04-21 at 16:17 +0800, Aaron Lu wrote:
> > > On Thu, Apr 21, 2022 at 03:49:21PM +0800, ying.huang@intel.com wrote:
>
> ... ...
>
> > > > For swap-in latency, we can use pmbench, which can output latency
> > > > information.
> > > >
> > >
> > > OK, I'll give pmbench a run, thanks for the suggestion.
> >
> > Better to construct a senario with more swapin than swapout. For
> > example, start a memory eater, then kill it later.
>
> What about vm-scalability/case-swapin?
> https://git.kernel.org/pub/scm/linux/kernel/git/wfg/vm-scalability.git/tree/case-swapin
>
> I think you are pretty familiar with it but still:
> 1) it starts $nr_task processes and each mmaps $size/$nr_task area and
> then consumes the memory, after this, it waits for a signal;
> 2) start another process to consume $size memory to push the memory in
> step 1) to swap device;
> 3) kick processes in step 1) to start accessing their memory, thus
> trigger swapins. The metric of this testcase is the swapin throughput.
>
> I plan to restrict the cgroup's limit to $size.
>
> Considering there is only one NVMe drive attached to node 0, I will run
> the test as described before:
> 1) bind processes to run on node 0, allocate on node 1 to test the
> performance when reclaimer's node id is the same as swap device's.
> 2) bind processes to run on node 1, allocate on node 0 to test the
> performance when page's node id is the same as swap device's.
>
> Ying and Yang,
>
> Let me know what you think about the case used and the way the test is
> conducted.
The test case looks good to me. And, do you have a way to measure swap
in latency? Better to compare between enabling and disabling per-node
swap device support too to make sure per-node support has performance
impact on this system.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2022-04-22 6:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 2:09 Yang Shi
2022-04-07 7:52 ` Michal Hocko
2022-04-07 17:27 ` Yang Shi
2022-04-07 8:13 ` Aaron Lu
2022-04-07 17:36 ` Yang Shi
2022-04-20 8:33 ` Aaron Lu
2022-04-20 22:21 ` Yang Shi
2022-04-21 7:34 ` Aaron Lu
2022-04-21 7:49 ` ying.huang
2022-04-21 8:17 ` Aaron Lu
2022-04-21 8:30 ` Aaron Lu
2022-04-21 8:34 ` ying.huang
2022-04-22 6:24 ` Aaron Lu
2022-04-22 6:27 ` ying.huang [this message]
2022-04-22 6:43 ` Aaron Lu
2022-04-22 7:26 ` ying.huang
2022-04-22 17:00 ` Yang Shi
2022-04-23 3:22 ` Aaron Lu
2022-04-29 10:26 ` Aaron Lu
2022-04-29 19:07 ` Yang Shi
2022-04-21 14:11 ` Aaron Lu
2022-04-21 17:19 ` Yang Shi
2022-04-21 23:57 ` ying.huang
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=4f1bc4dc65117a185833555ff8df30a944453499.camel@intel.com \
--to=ying.huang@intel.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shy828301@gmail.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