public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>
Cc: arjan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: Core kernel parameters and /sys/parameters?
Date: Fri, 15 Aug 2008 09:32:43 +1000	[thread overview]
Message-ID: <200808150932.44204.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080814222522.GO30057@kroah.com>

On Friday 15 August 2008 08:25:22 Greg KH wrote:
> On Thu, Jul 31, 2008 at 01:59:02PM +1000, Rusty Russell wrote:
> > Hi Greg,
> >
> >    Was looking at implementing "core_param" for things like
> > "initcall_debug" (ie. params with no prefix), and wanted to put them in
> > sysfs of course.  I hacked in a new "kernel" dir, but
> > /sys/module/kernel/parameters/ is a bit of an odd place for it to end up
> > in.
> >
> >    I noticed this comment in params.c:
> >
> >  * /sys/module/[mod->name]/parameters to /sys/parameters/[mod->name]/
> >
> > I like the idea of /sys/parameters/ much better (perhaps even with core
> > parameters at the top level).  Is this obsolete?  Planned?
>
> Did I write that comment?  I sure don't remember it, sorry :)
>
> I don't have any plans on changing this, but I do know people use the
> /sys/module/MODULE_NAME/parameters interface today, why change it?

Well mainly that many of them aren't modules, so if a change was planned for 
some other reason I'd support it.

And as I said, having core parameters (ie. converting things which are current 
__setup) appear in /sys/module/kernel/parameters/ is a bit strange.

Cheers,
Rusty.

  reply	other threads:[~2008-08-14 23:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  3:59 Core kernel parameters and /sys/parameters? Rusty Russell
2008-08-14 22:25 ` Greg KH
2008-08-14 23:32   ` Rusty Russell [this message]
2008-08-15  2:16     ` Marcel Holtmann

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=200808150932.44204.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=arjan@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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