From: Andi Kleen <ak@suse.de>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, steiner@sgi.com
Subject: Re: [PATCH] - Externel SLIT table information thru sysfs
Date: 25 Nov 2004 12:12:04 +0100 [thread overview]
Message-ID: <p73r7miuqrf.fsf@brahms.suse.de> (raw)
In-Reply-To: <34iNY-3nm-27@gated-at.bofh.it>
Greg KH <greg@kroah.com> writes:
> > > 10 20 64 42 42 22
>
> Care to turn this into a one value per file implementation instead of
> this? That will make it easier to determine exactly what the data in
> each file is, and follow the sysfs rules.
No, we discussed this already earlier (please check the thread)
One file for each would lead to excessive memory consumption on large
systems, and it would make it much more costly for programs to read
this information.
Also the sysfs documentation allows for this case where it makes
sense even.
-Andi
next parent reply other threads:[~2004-11-27 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34a45-4B7-9@gated-at.bofh.it>
[not found] ` <34hyB-2nd-21@gated-at.bofh.it>
[not found] ` <34iNY-3nm-27@gated-at.bofh.it>
2004-11-25 11:12 ` Andi Kleen [this message]
2004-11-24 16:57 [PATCH] - Externel SLIT table information thru sysfs Jack Steiner
2004-11-25 2:04 ` Randy.Dunlap
2004-11-25 3:39 ` Greg KH
2004-11-26 3:54 ` Jack Steiner
2004-11-25 14:00 ` Jack Steiner
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=p73r7miuqrf.fsf@brahms.suse.de \
--to=ak@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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