From: Jim Cromie <jim.cromie@gmail.com>
To: linux-mm@kvack.org
Cc: gregkh@linuxfoundation.org, linux@rasmusvillemoes.dk,
Jim Cromie <jim.cromie@gmail.com>,
Jason Baron <jbaron@akamai.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/7] dyndbg: count repetition in __dyndbg_callsite fields.
Date: Wed, 25 Nov 2020 12:36:21 -0700 [thread overview]
Message-ID: <20201125193626.2266995-3-jim.cromie@gmail.com> (raw)
In-Reply-To: <20201125193626.2266995-1-jim.cromie@gmail.com>
The __dyndbg_callsite section is basically a flat db-table, an array
of struct _ddebug_callsite[]s. Its data is inherently hierarchical
and sorted, so a field-wise run-length encoding would compress well.
Add counters and code to test 3 fields of consecutive callsites for
repeated values. The results inform a compression estimate.
dyndbg: 2605 entries. repeated entries: 2369 module 2231 file 1147 func
Thats (91%, 86%, 44%) repeated values in those pointers/columns, on my
i7 laptop build. With a zero-overhead markup, like LSB-stealing, we
could mark the differing tails of consecutive records, and get 11/24
compression on init/main pr_debugs.
For a slightly apples-to-oranges comparison (text vs pointers),
`gzip /proc/dynamic_debug/control` achieves 6/1 compression.
Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
---
lib/dynamic_debug.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index 2e4a39c349a5..5980d44ff2f8 100644
--- a/lib/dynamic_debug.c
+++ b/lib/dynamic_debug.c
@@ -1081,11 +1081,12 @@ static int __init dynamic_debug_init_control(void)
static int __init dynamic_debug_init(void)
{
- struct _ddebug *iter, *iter_start;
+ struct _ddebug *iter, *iter_start, *prev = NULL;
const char *modname = NULL;
char *cmdline;
int ret = 0;
int n = 0, entries = 0, modct = 0;
+ int modreps = 0, funcreps = 0, filereps = 0;
if (&__start___dyndbg == &__stop___dyndbg) {
if (IS_ENABLED(CONFIG_DYNAMIC_DEBUG)) {
@@ -1099,7 +1100,16 @@ static int __init dynamic_debug_init(void)
iter = __start___dyndbg;
modname = iter->site->modname;
iter_start = iter;
- for (; iter < __stop___dyndbg; iter++) {
+ for (prev = iter; iter < __stop___dyndbg; iter++) {
+ if (entries) {
+ if (prev->site->modname == iter->site->modname)
+ modreps++;
+ if (prev->site->function == iter->site->function)
+ funcreps++;
+ if (prev->site->filename == iter->site->filename)
+ filereps++;
+ prev++; /* one behind iter */
+ }
entries++;
if (strcmp(modname, iter->site->modname)) {
modct++;
@@ -1122,6 +1132,9 @@ static int __init dynamic_debug_init(void)
(int)(entries * sizeof(struct _ddebug)),
(int)(entries * sizeof(struct _ddebug_callsite)));
+ vpr_info("%d entries. repeated entries: %d module %d file %d func\n",
+ entries, modreps, filereps, funcreps);
+
/* apply ddebug_query boot param, dont unload tables on err */
if (ddebug_setup_string[0] != '\0') {
pr_warn("ddebug_query param name is deprecated, change it to dyndbg\n");
--
2.28.0
next prev parent reply other threads:[~2020-11-25 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201125193626.2266995-1-jim.cromie@gmail.com>
2020-11-25 19:36 ` [PATCH 1/7] dyndbg: move struct _ddebug's display fields to new _ddebug_callsite Jim Cromie
2020-11-25 19:36 ` Jim Cromie [this message]
2020-11-25 19:36 ` [PATCH 3/7] dyndbg: add some code to see alignments of linkage data Jim Cromie
2020-11-25 19:36 ` [PATCH 4/7] dyndbg: select ZPOOL,ZS_MALLOC in Kconfig.debug DYNAMIC_DEBUG_CORE Jim Cromie
2020-11-25 19:36 ` [PATCH 5/7] dyndbg: replace __dyndbg_callsite section with a zs-pool copy Jim Cromie
2020-11-25 19:36 ` [PATCH 6/7] dyndbg: add locking around zpool-add loop in zpool-init Jim Cromie
2020-11-25 19:36 ` [PATCH 7/7] dyndbg: enable 'cache' of active pr_debug callsites Jim Cromie
2020-11-25 20:54 ` Jason Baron
2020-11-25 21:23 ` jim.cromie
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=20201125193626.2266995-3-jim.cromie@gmail.com \
--to=jim.cromie@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
/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).