From: Valdis.Kletnieks@vt.edu
To: Georgi Chorbadzhiyski <gf@unixsol.org>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com,
jsimmons@infradead.org, rubini@vision.unipv.it,
vandrove@vc.cvut.cz
Subject: sysfs file size wierdness (was Re: 2.6-test1-mm1 success, tiny mouse and framebuffer problems
Date: Wed, 16 Jul 2003 12:11:36 -0400 [thread overview]
Message-ID: <200307161611.h6GGBaLf004493@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 16 Jul 2003 17:47:02 +0300." <3F156566.4040206@unixsol.org>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Wed, 16 Jul 2003 17:47:02 +0300, Georgi Chorbadzhiyski said:
> P.S. Every file in sysfs is 4096 bytes, is this normal?
Even better:
# ls -l /sys/devices/system/cpu/cpu0/cpufreq
total 0
-r--r--r-- 1 root root 4096 Jul 16 09:59 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 Jul 16 09:59 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 Jul 16 09:59 scaling_available_governors
-r--r--r-- 1 root root 4096 Jul 16 09:59 scaling_driver
-rw-r--r-- 1 root root 4096 Jul 16 09:59 scaling_governor
-rw-r--r-- 1 root root 4096 Jul 16 09:59 scaling_max_freq
-rw-r--r-- 1 root root 4096 Jul 16 09:59 scaling_min_freq
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
performance
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance powersave
# echo powersave >| /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# ls -l /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
-rw-r--r-- 1 root root 0 Jul 16 09:59 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Started off as 4096, writing makes it go to zero. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-07-16 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 14:47 2.6-test1-mm1 success, tiny mouse and framebuffer problems Georgi Chorbadzhiyski
2003-07-16 16:11 ` Valdis.Kletnieks [this message]
2003-07-16 16:18 ` sysfs file size wierdness (was " Oliver Neukum
2003-07-16 17:27 ` Greg KH
2003-07-16 18:47 ` Georgi Chorbadzhiyski
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=200307161611.h6GGBaLf004493@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@digeo.com \
--cc=gf@unixsol.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@vision.unipv.it \
--cc=vandrove@vc.cvut.cz \
/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;
as well as URLs for NNTP newsgroup(s).