public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Thaeter <ct@pipapo.org>
To: linux-kernel@vger.kernel.org
Cc: Pavel Machek <pavel@ucw.cz>, eric.piel@tremplin-utc.net
Subject: [PATCH] hpfall.c improvements, thoughts
Date: Wed, 25 Mar 2009 22:27:59 +0100	[thread overview]
Message-ID: <49CAA1DF.8060109@pipapo.org> (raw)
In-Reply-To: <20090324211555.GA24172@elf.ucw.cz>

Some conversation I had with Pavel,

imo the example code should be at least barely useable as in not causing
harm like I sketched in (1.). Maybe someone else picks that up and
improves it later on. Patch at the end, quite sketchy and imature as it
doesn't check for errors, but certainly better than before.


	Christian


Pavel Machek wrote:
> Hi!
> 
>> I just hacked and installed the hpfall utility a little bit. By that I
>> thought I should share some ideas with you. (made no patch since this is
>> trivial, but important)
>>
>> 1. hpfall *MUST* mlockall(MCL_CURRENT|MCL_FUTURE); itself!
>> Since the Program sits and waits most of the time it becomes very likely
>> swapped out. If it gets woken up when the laptop drops from the table
>> while it is swapped out it actually triggers harddrive activity!
>>
>> 2. daemon(0, 0);  ... Quick and dirty way to daemonize it
>>
>> 3. Realtime priority:
>>  param.sched_priority = sched_get_priority_max(SCHED_FIFO);
>>  sched_setscheduler(0, SCHED_FIFO, &param);
>> Should give a chance that it has less latency when woken up.
> 
> Good ideas. I ommited them, thinking that someone else will do it. Can
> you submit a patch? (akpm, cc: lk, Eric Piel) I no longer have the
> hardware, and would prefer not to patch code I can't test.
> 
>> .. another thing is that I still use the old IDE driver, I just changed
>> sda to hda, maybe a bandaid is to use argv[1] for defining the drive
>> (well I understand that it is very basic example code, so maybe someday
>> someone adds a better option parser)
> 
> Option parser would indeed be nice.
> 								Pavel
>


Signed-off-by: Christian Thaeter <ct@pipapo.org>
---

diff --git a/Documentation/hwmon/hpfall.c b/Documentation/hwmon/hpfall.c
index bbea1cc..f3cde67 100644
--- a/Documentation/hwmon/hpfall.c
+++ b/Documentation/hwmon/hpfall.c
@@ -16,6 +16,8 @@
 #include <stdint.h>
 #include <errno.h>
 #include <signal.h>
+#include <sys/mman.h>
+#include <sched.h>

 void write_int(char *path, int i)
 {
@@ -63,6 +65,7 @@ void ignore_me(void)
 int main(int argc, char* argv[])
 {
        int fd, ret;
+       struct sched_param param;

        fd = open("/dev/freefall", O_RDONLY);
        if (fd < 0) {
@@ -70,7 +73,12 @@ int main(int argc, char* argv[])
                return EXIT_FAILURE;
        }

-	signal(SIGALRM, ignore_me);
+       daemon(0,0);
+       param.sched_priority = sched_get_priority_max(SCHED_FIFO);
+       sched_setscheduler(0, SCHED_FIFO, &param);
+       mlockall(MCL_CURRENT|MCL_FUTURE);
+
+       signal(SIGALRM, ignore_me);

        for (;;) {
 	       unsigned char count;


       reply	other threads:[~2009-03-25 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49C8F338.7030901@pipapo.org>
     [not found] ` <20090324211555.GA24172@elf.ucw.cz>
2009-03-25 21:27   ` Christian Thaeter [this message]
2009-03-25 21:33     ` [PATCH] hpfall.c improvements, thoughts Pavel Machek
2009-05-20 21:04     ` Éric Piel

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=49CAA1DF.8060109@pipapo.org \
    --to=ct@pipapo.org \
    --cc=eric.piel@tremplin-utc.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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