From: Stefan Roesch <shr@devkernel.io>
To: kernel-team@fb.com
Cc: shr@devkernel.io, david@redhat.com, oliver.sang@intel.com,
linux-mm@kvack.org, ltp@lists.linux.it, pvorel@suse.cz,
liwang@redhat.com
Subject: [PATCH v2 0/2] KSM: support smart-scan feature
Date: Fri, 1 Dec 2023 13:09:28 -0800 [thread overview]
Message-ID: <20231201210930.2651725-1-shr@devkernel.io> (raw)
This patch series makes two changes:
- Disable the smart-scan feature for ksm01 - ksm04
This is necessary to make sure that the volatile metrics have the
expected counts.
- Add a new test for the smart-scan feature
The new test verifies that the smart-scan feature skips pages when it has
been enabled for a VMA.
Versions:
- V2:
- Disable smart_scan in the test setup structure
- Remove the changes in create_same_memory()
- Add the new testcase ksm07 for the smart scan test
Stefan Roesch (2):
mem: disable KSM smart scan for ksm tests
add ksm test for smart-scan feature
testcases/kernel/mem/.gitignore | 1 +
testcases/kernel/mem/include/mem.h | 1 +
testcases/kernel/mem/ksm/ksm01.c | 2 +
testcases/kernel/mem/ksm/ksm02.c | 2 +
testcases/kernel/mem/ksm/ksm03.c | 2 +
testcases/kernel/mem/ksm/ksm04.c | 2 +
testcases/kernel/mem/ksm/ksm07.c | 69 +++++++++++++++++++++++++++++
testcases/kernel/mem/lib/mem.c | 70 ++++++++++++++++++++++++++++++
8 files changed, 149 insertions(+)
create mode 100644 testcases/kernel/mem/ksm/ksm07.c
base-commit: 8c89ef3d451087ed6e18750bd5eedd10e5ab3d2e
--
2.39.3
next reply other threads:[~2023-12-01 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 21:09 Stefan Roesch [this message]
2023-12-01 21:09 ` [PATCH v2 1/2] mem: disable KSM smart scan for ksm tests Stefan Roesch
2023-12-04 10:45 ` Petr Vorel
2023-12-04 18:38 ` Stefan Roesch
2023-12-04 18:38 ` Stefan Roesch
2023-12-01 21:09 ` [PATCH v2 2/2] add ksm test for smart-scan feature Stefan Roesch
2023-12-04 9:21 ` Petr Vorel
2023-12-04 18:41 ` Stefan Roesch
2023-12-04 10:39 ` Petr Vorel
2023-12-04 18:42 ` Stefan Roesch
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=20231201210930.2651725-1-shr@devkernel.io \
--to=shr@devkernel.io \
--cc=david@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=oliver.sang@intel.com \
--cc=pvorel@suse.cz \
/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).