From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Young <hidave.darkstar@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH -mm] x86 boot : export boot_params via sysfs (forward to Greg)
Date: Wed, 12 Dec 2007 14:15:35 -0500 [thread overview]
Message-ID: <20071212191535.GB31044@redhat.com> (raw)
In-Reply-To: <20071212174507.GB16049@kroah.com>
On Wed, Dec 12, 2007 at 09:45:07AM -0800, Greg Kroah-Hartman wrote:
> Well, I respectively disagree. sysfs is NOT for exporting various
> binary kernel structures to userspace directly. Again, the binary files
> in sysfs are for chunks of memory that are PASS-THROUGH from hardware to
> userspace, with no kernel intervention at all.
> If you really need such a thing, use debugfs, as the only rule for
> debugfs is that there is no rules :)
Whilst on the subject, why wasn't /sys/slab done in debugfs ?
The one-value-per-file thing has gone taken to ridiculous extremes there.
Having 3641 sysfs files that most people never use permanently taking up
memory seems to be a massive waste of resources.
Nearly a third of all the sysfs files I have on my system belong to that
subtree, which is just.. wow.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-12-12 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1197443265.14443.59.camel@caritas-dev.intel.com>
[not found] ` <20071212073502.GA31348@kroah.com>
[not found] ` <1197447079.14443.82.camel@caritas-dev.intel.com>
2007-12-12 17:45 ` [PATCH -mm] x86 boot : export boot_params via sysfs (forward to Greg) Greg KH
2007-12-12 19:15 ` Dave Jones [this message]
2007-12-12 22:18 ` Greg KH
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=20071212191535.GB31044@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=greg@kroah.com \
--cc=hidave.darkstar@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.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 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.