From: Peng Liu <liupeng256@huawei.com>
To: <glider@google.com>, <elver@google.com>, <dvyukov@google.com>,
<corbet@lwn.net>, <sumit.semwal@linaro.org>,
<christian.koenig@amd.com>, <akpm@linux-foundation.org>
Cc: <kasan-dev@googlegroups.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linaro-mm-sig@lists.linaro.org>,
<linux-mm@kvack.org>, <liupeng256@huawei.com>
Subject: [PATCH RFC 0/3] Add a module parameter to adjust kfence objects
Date: Mon, 24 Jan 2022 02:52:02 +0000 [thread overview]
Message-ID: <20220124025205.329752-1-liupeng256@huawei.com> (raw)
This series make KFENCE to be more convenient to adjust parameters in
not only debug process but also production situations. In different
production and development stage, the demands of memory and CPU
limitations for KFENCE is quite different. In order to satisfy these
demands with a uniform kernel release, dynamically adjust KFENCE
parameters is needed.
Signed-off-by: Peng Liu <liupeng256@huawei.com>
Peng Liu (3):
kfence: Add a module parameter to adjust kfence objects
kfence: Optimize branches prediction when sample interval is zero
kfence: Make test case compatible with run time set sample interval
Documentation/dev-tools/kfence.rst | 14 ++--
include/linux/kfence.h | 10 ++-
mm/kfence/core.c | 113 ++++++++++++++++++++++++-----
mm/kfence/kfence.h | 2 +-
mm/kfence/kfence_test.c | 10 +--
5 files changed, 116 insertions(+), 33 deletions(-)
--
2.18.0.huawei.25
next reply other threads:[~2022-01-24 2:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 2:52 Peng Liu [this message]
2022-01-24 2:52 ` [PATCH RFC 1/3] kfence: " Peng Liu
2022-01-24 8:19 ` Marco Elver
2022-01-24 11:24 ` liupeng (DM)
2022-01-24 11:32 ` Dmitry Vyukov
2022-01-24 11:45 ` Marco Elver
2022-01-24 11:55 ` Marco Elver
2022-01-26 12:09 ` liupeng (DM)
2022-01-24 2:52 ` [PATCH RFC 2/3] kfence: Optimize branches prediction when sample interval is zero Peng Liu
2022-01-24 8:20 ` Marco Elver
2022-01-24 2:52 ` [PATCH RFC 3/3] kfence: Make test case compatible with run time set sample interval Peng Liu
2022-01-24 8:25 ` Marco Elver
2022-01-24 12:18 ` liupeng (DM)
2022-01-24 12:21 ` Marco Elver
2022-01-26 12:12 ` liupeng (DM)
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=20220124025205.329752-1-liupeng256@huawei.com \
--to=liupeng256@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sumit.semwal@linaro.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