From: Greg KH <greg@kroah.com>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Mike Waychison <Michael.Waychison@Sun.COM>,
linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Thu, 16 Dec 2004 17:23:01 -0800 [thread overview]
Message-ID: <20041217012301.GA12553@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0412170204480.25628@alpha.polcom.net>
On Fri, Dec 17, 2004 at 02:15:22AM +0100, Grzegorz Kulewski wrote:
> >>And polluting / with proc, sys, dev, selinux, debug and who knows what
> >>else is at least equally bad.
> >
> >Why? Each location is defined to have one, specific, well defined thing
> >there that people can count on (or not count on in the case of /debug.)
>
> Because in short time we will end with / occupying >1 page of console -
> and it will be bad in my opinion. Besides do we really need that many
> fses - each for exporting kernel data to userspace?
Yes, we do.
> This is at least strange. Why can not /dev, /selinux be merged into
> /sys (ok, maybe there should be symlinks in /dev to devices in right
> device directory in /sys).
Because all three of them are radically different things.
> And I have also other question: Where can I find some info about using
> /sys (in kernel)
Documentation/driver-model/* is a good start. It's a bit out of date,
but better than nothing. The lwn.net series of articles is also good to
look at.
> and some small note about its implementation and overhead (cpu and
> memory)?
For that you will have to look at the code itself.
Good luck,
greg k-h
next prev parent reply other threads:[~2004-12-17 1:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 19:00 debugfs in the namespace Pete Zaitcev
2004-12-16 19:08 ` Greg KH
2004-12-16 19:33 ` Pete Zaitcev
2004-12-16 19:42 ` Greg KH
2004-12-17 19:08 ` Pavel Machek
2004-12-18 17:49 ` Jörn Engel
2004-12-16 20:00 ` Jan Engelhardt
2004-12-16 21:51 ` Mike Waychison
2004-12-16 22:18 ` Greg KH
2004-12-16 22:45 ` Pete Zaitcev
2004-12-16 22:53 ` Greg KH
2004-12-16 23:39 ` Grzegorz Kulewski
2004-12-16 23:51 ` Greg KH
2004-12-17 0:08 ` Grzegorz Kulewski
2004-12-17 0:21 ` Greg KH
2004-12-17 1:15 ` Grzegorz Kulewski
2004-12-17 1:23 ` Greg KH [this message]
2004-12-17 7:48 ` Jan Engelhardt
2004-12-16 23:21 ` Bernd Eckenfels
2004-12-17 2:27 ` Phil Lougher
2004-12-17 7:23 ` Jan Engelhardt
2004-12-17 17:22 ` debugfs in the namespace [u] Martin Schlemmer [c]
2004-12-16 23:29 ` debugfs in the namespace Pedro Venda (SYSADM)
2004-12-18 22:24 ` Matt Mackall
2004-12-17 4:06 ` H. Peter Anvin
2004-12-17 18:39 ` John Levon
[not found] <fa.al1ango.pl0rak@ifi.uio.no>
[not found] ` <fa.ddml8me.1k46obg@ifi.uio.no>
2004-12-17 5:51 ` Bodo Eggert
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=20041217012301.GA12553@kroah.com \
--to=greg@kroah.com \
--cc=Michael.Waychison@Sun.COM \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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