From: jim.cromie@gmail.com
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: is there an efficient module_is_builtin() test ?
Date: Tue, 9 Mar 2021 12:55:14 -0700 [thread overview]
Message-ID: <CAJfuBxxS+x6sWyi5XUW16555MCj=E+-C9usfUNh6RV-Yvv2duw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 763 bytes --]
Im trying to reduce memory used by
internal tables built into DYNAMIC_DEBUG
the main savings available is in the per pr_debug*
callsite data: modname, filename, funcname.
I have segregated those fields to a new __dyndbg_sites section,
described by struct _ddebug_site, and now refd by new ptr in
struct _ddebug
That new ptr enlarges the memory footprint, so I want to replace it
with an integer index into the section / array. Existing padding could
hold the index.
To use the index, I need &dyndbg_sites[], and that only works
for builtin-module's callsites. For loaded modules, I can/have
added a pointer to the section into module load_info, giving me
the base I will need for the ! builtin branch.
I just need a not expensive is-it-builtin (modref)
[-- Attachment #1.2: Type: text/html, Size: 1039 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2021-03-09 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 19:55 jim.cromie [this message]
2021-03-09 22:25 ` is there an efficient module_is_builtin() test ? Valdis Klētnieks
2021-03-17 4:59 ` 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='CAJfuBxxS+x6sWyi5XUW16555MCj=E+-C9usfUNh6RV-Yvv2duw@mail.gmail.com' \
--to=jim.cromie@gmail.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).