Linux Documentation
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: patches@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: admin: reorganize kernel-parameters intro
Date: Mon, 28 Oct 2024 10:59:43 +0700	[thread overview]
Message-ID: <Zx8ML4Q6GyGPw-sy@archie.me> (raw)
In-Reply-To: <20241028005356.214369-1-rdunlap@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

On Sun, Oct 27, 2024 at 05:53:56PM -0700, Randy Dunlap wrote:
> +This document may not be entirely up to date and comprehensive. The command
> +"modinfo -p ${modulename}" shows a current list of all parameters of a loadable
> +module. Loadable modules, after being loaded into the running kernel, also
> +reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
> +parameters may be changed at runtime by the command
> +``echo -n ${value} > /sys/module/${modulename}/parameters/${parm}``.

How can users get support for parameters not documented here? Post to LKML
(and hoping that they also Cc: relevant maintainers and mailing list)?

> +KMG suffixes
> +~~~~~~~~~~~~
> +
> +The [KMG] suffix is commonly described after a number of kernel
> +parameter values. These 'K', 'M', and 'G' letters represent the _binary_
> +multipliers 'Kilo', 'Mega', and 'Giga', equaling 2^10, 2^20, and 2^30
> +bytes respectively. Such letter suffixes can also be entirely omitted.
> +

Metric suffixes?

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-10-28  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28  0:53 [PATCH] Documentation: admin: reorganize kernel-parameters intro Randy Dunlap
2024-10-28  3:59 ` Bagas Sanjaya [this message]
2024-10-28  4:27   ` Randy Dunlap
2024-10-28  6:11     ` Bagas Sanjaya

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=Zx8ML4Q6GyGPw-sy@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=rdunlap@infradead.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