From: David Decotigny <david.decotigny@google.com>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Randy Dunlap <rdunlap@xenotime.net>,
Michal Schmidt <mschmidt@redhat.com>,
Linus Walleij <linus.walleij@stericsson.com>,
David Decotigny <david.decotigny@google.com>
Subject: [PATCH v1 0/3] param: configurable /sys/module/*/paramaters
Date: Wed, 26 Oct 2011 19:22:24 -0700 [thread overview]
Message-ID: <cover.1319679966.git.david.decotigny@google.com> (raw)
These changes allow to compile kernels with sysfs but without
/sys/module/*/paramaters/. This should allow:
- on small systems: no memory pressure caused by unneeded sysfs
attributes.
- on large systems: more modules could be converted to have their
perm != 0 in module_param(): better for audit, debug, etc. For
example, on my copy, 1658 module attributes have perm == 0,
presumably to spare some memory, but it can be interesting to have
access to those at runtime.
By default, /sys/module/*/paramaters/ is enabled, but can be disabled
in expert mode (CONFIG_SYSFS_MODULE_PARAM is not set).
David Decotigny (3):
param: make destroy_params() private
param: simple refactoring
param: allow to selectively enable /sys/module/MOD/paramaters nodes
fs/sysfs/Kconfig | 15 ++++++-
include/linux/moduleparam.h | 14 +-----
kernel/module.c | 9 ++++
kernel/params.c | 108 +++++++++++++++++++++----------------------
4 files changed, 77 insertions(+), 69 deletions(-)
--
1.7.3.1
next reply other threads:[~2011-10-27 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 2:22 David Decotigny [this message]
2011-10-27 2:22 ` [PATCH v1 1/3] param: make destroy_params() private David Decotigny
2011-10-27 2:22 ` [PATCH v1 2/3] param: simple refactoring David Decotigny
2011-10-27 2:22 ` [PATCH v1 3/3] param: allow to selectively enable /sys/module/MOD/paramaters nodes David Decotigny
2011-10-31 1:42 ` Rusty Russell
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=cover.1319679966.git.david.decotigny@google.com \
--to=david.decotigny@google.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.