From: Pavel Machek <pavel@ucw.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Create new LED trigger for CPU activity
Date: Fri, 7 Jul 2006 01:52:04 +0200 [thread overview]
Message-ID: <20060706235204.GB4821@elf.ucw.cz> (raw)
In-Reply-To: <20060706191603.GA13898@phoenix>
Hi!
> This patch creates a new LED trigger that triggers whenever the CPU is
> active. It can be configured with module parameters to trigger on any
> combination of user, nice, system, or iowait time, and defaults to
> including user and system time but not nice or iowait time. I've tested
> it a bit, and it seems to work, but no guarantees. It's diffed against
> 2.6.17-git25.
>
> Signed-off-by: Thomas Tuttle <thinkinginbinary@gmail.com>
I like the idea.. CPU usage led is very useful, and old led system
actually provided it. But...
> +/*
> + * ChangeLog:
> + *
> + * Revision 3 (2006/06/06):
> + * Added module parameters to configure which time is counted as CPU
> + * activity. (thanks to Andrew Morton)
> + *
> + * Revision 2 (2006/06/05):
> + * Diffed against 2.6.17-git25 instead of 2.6.17.1.
> + * Fixed several code style issues (thanks to Randy Dunlap)
> + *
> + * Revision 1 (2006/06/05):
> + * Initial patch submitted.
> + */
Please don't include changelogs in sources.
> +#define UPDATE_INTERVAL (5) /* delay between updates, in ms */
Polling every 5 msec is going to cost _lot_ of juice. Is there a
better way?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-07-06 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 19:16 Thomas Tuttle
2006-07-06 23:52 ` Pavel Machek [this message]
2006-07-07 1:58 ` Thomas Tuttle
2006-07-07 7:54 ` Richard Purdie
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=20060706235204.GB4821@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®