From: Martin von Gagern <Martin.vGagern@gmx.net>
To: cpufreq@vger.kernel.org
Subject: ignore_nice vs. ignore_nice_load
Date: Fri, 02 Aug 2013 22:40:21 +0200 [thread overview]
Message-ID: <51FC1935.5030702@gmx.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
I just noticed that recently (apparently since 4d5dcc4211f9def4) the
sysfs file that used to be called ignore_nice_load is now called
ignore_nice. I don't know why this was renamed, but what has me
worried even more is the fact that the documentation in
Documentation/cpu-freq/governors.txt wasn't updated accordingly: it
still talks about ignore_nice_load. It would be beter to synchronize
these two again.
Investigating this issue, I also found that the file used to be called
ignore_nice in the past, but at that point apparently had an inverted
meaning. The node was renamed deliberately in 001893cda2f280ab when
the semantics changed. I can't help but wonder whether anyone might
now get confused with this old name popping up again, after all this
time. Either name is fine by me, but I am surprised nevertheless.
I hope I can get this message through without being subscribed to the
list. I would be happy if you could cc me on any replies, but as long
as someone will eventually take care of things, you may also choose to
discuss this on the list without me. I doubt I can contribute any more.
Greetings,
Martin von Gagern
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlH8GTUACgkQRhp6o4m9dFtKXgCcD7Kr20vJACKsPnTM7dv1Rn0s
/I4An2uqLZaF08+RpTwxZ4hg26/WBVbX
=mBWO
-----END PGP SIGNATURE-----
next reply other threads:[~2013-08-02 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 20:40 Martin von Gagern [this message]
2013-08-05 7:01 ` ignore_nice vs. ignore_nice_load Viresh Kumar
2013-08-05 13:00 ` Rafael J. Wysocki
2013-08-06 7:40 ` Martin von Gagern
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=51FC1935.5030702@gmx.net \
--to=martin.vgagern@gmx.net \
--cc=cpufreq@vger.kernel.org \
/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.