From: Pavel Machek <pavel@suse.cz>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Samium Gromoff <_deepfire@mail.ru>,
Dominik Kubla <kubla@sciobyte.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Laptop harddisk spindown?
Date: Sat, 1 Jan 2000 00:31:48 +0000 [thread overview]
Message-ID: <20000101003147.C35@(none)> (raw)
In-Reply-To: <200111080502.fA852im17980@vegae.deep.net> <1005221273.13841.19.camel@nomade>
In-Reply-To: <1005221273.13841.19.camel@nomade>; from xavier.bestel@free.fr on Thu, Nov 08, 2001 at 01:07:52PM +0100
Hi!
> > > > i have a disk access _every_ 5 sec, unregarding the system load,
> > > > 24x7x365, so i suppose while it doesnt hurts me, it hurts folks with power
> > > > bound boxes...
>
> That's a kernel daemon called kupdated. Under Linux buffers are flushed
> every 5 seconds (I don't like this myself, it should be triggered by
> something dependant on free mem, dirty buffers, disk access, etc. but
> not time, this doesn't scale.
>
> Under 2.2 you can try the noflushd package - perhaps it works on 2.4, I
> haven't tried. It works more or less.
noflushd does work on 2.4
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-11-10 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011108002154.D7288@duron.intern.kubla.de>
2001-11-08 5:02 ` Laptop harddisk spindown? Samium Gromoff
2001-11-08 12:07 ` Xavier Bestel
2000-01-01 0:31 ` Pavel Machek [this message]
2001-11-08 12:24 ` Sven Koch
2001-11-11 1:42 ` Tim Connors
2001-11-08 18:08 Thomas Hood
-- strict thread matches above, loose matches on Subject: below --
2001-11-07 22:51 Samium Gromoff
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='20000101003147.C35@(none)' \
--to=pavel@suse.cz \
--cc=_deepfire@mail.ru \
--cc=kubla@sciobyte.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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