[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200710241648.55939.nickpiggin@yahoo.com.au>
Date: Wed, 24 Oct 2007 16:48:55 +1000
From: Nick Piggin <nickpiggin@...oo.com.au>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: Takenori Nagano <t-nagano@...jp.nec.com>
Subject: sysfs sys/kernel/ namespace (was Re: [PATCH 0/2] add new notifier function ,take2)
On Tuesday 23 October 2007 10:55, Takenori Nagano wrote:
> Nick Piggin wrote:
> > One thing I'd suggest is not to use debugfs, if it is going to
> > be a useful end-user feature.
>
> Is /sys/kernel/notifier_name/ an appropriate place?
Hi list,
I'm curious about the /sys/kernel/ namespace. I had presumed that
it is intended to replace /proc/sys/ basically with the same
functionality. I _assume_ these are system software stats and
tunables that are not exactly linked to device drivers (OTOH,
where do you draw the line? eg. Would filesystems go here? Core
network algorithm tunables might, but per interface ones probably
not...).
I don't know. Is there guidelines for sysfs (and procfs for that
matter)? Is anyone maintaining it (not the infrastructure, but
the actual content)?
It's kind of ironic that /proc/sys/ looks like one of the best
organised directories in proc, while /sys/kernel seems to be in
danger of becoming a mess: it has kexec and uevent files in the
base directory, rather than in subdirectories...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists