From: Bart Samwel <bart@samwel.tk>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Attempt at laptop-mode for 2.6.0
Date: Tue, 23 Dec 2003 19:48:56 +0100 [thread overview]
Message-ID: <3FE88E18.7080507@samwel.tk> (raw)
In-Reply-To: <20031223163810.GB23184@suse.de>
Jens Axboe wrote:
>>Even though I don't own a laptop, I find it very irritating that my hard
>>drive is active so much. Wanting to fix this, I found the Jens Axboe's
>>"laptop-mode" patch. Unfortunately it hadn't been ported to Linux
>>2.6.0 yet, and I'm using that as my primary kernel now. I gave porting
>>it a shot, and here is the result. I'm running it right now, and my hard
>>drive has been spun down for the complete time I have been writing this
>>message. Still, I'm not sure whether it really works as advertised. :)
>>The reason is that my PC is also a mail server for my personal e-mail,
>>and I receive e-mails more than once every 10 minutes (fscking spam!).
>>Still, the tests that I've done seem to indicate that it works.
>
> Thanks for getting this started. I'm not particularly fond of the
> behaviourial changes you made, I guess most are due to it being
> incomplete?
Is it only the block dirtyings that you're missing, or is there more? I
might have used an old 2.4 patch as reference -- what was the latest
version again?
> The block dirtying is the most interesting aspect of the dump
> functionality, reporting WRITEs don't give you the info you need
> to fix your setup.
OK, that depends on your point of view. At this point it weren't the
WRITEs that were interesting to me, it were the READs. The WRITEs just
came as a bonus. The reason: what bugged me during development were the
programs that read new data from disk, and I wanted to find out what to
turn off in order to keep the disk from spinning up all the time. And
when the disk DID spin up, I wanted to know if it was my fault or if it
was some daemon messing up my tests again. This is due to my not
actually working on a laptop but on a home server machine. :) I guess
that when you're going for disk-spindowns of longer than 10 minutes
(which is what the block dirtying dumps are for, presumably?) dirtyings
start to become interesting. I'll see if I can port that bit as well,
shouldn't be that much work.
Bart
prev parent reply other threads:[~2003-12-23 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 15:24 Attempt at laptop-mode for 2.6.0 Bart Samwel
2003-12-23 16:38 ` Jens Axboe
2003-12-23 18:48 ` Bart Samwel [this message]
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=3FE88E18.7080507@samwel.tk \
--to=bart@samwel.tk \
--cc=axboe@suse.de \
--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