From: Daniel Kobras <kobras@tat.physik.uni-tuebingen.de>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: Pavel Machek <pavel@suse.cz>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: spindown
Date: Sat, 23 Jun 2001 00:09:12 +0200 [thread overview]
Message-ID: <20010623000912.A415@pelks01.extern.uni-tuebingen.de> (raw)
In-Reply-To: <20010615152306.B37@toy.ucw.cz> <20010618222131.A26018@paranoidfreak.co.uk> <20010619124627.A202@bug.ucw.cz> <20010621180701.B4523@pcep-jamie.cern.ch>
In-Reply-To: <20010621180701.B4523@pcep-jamie.cern.ch>; from lk@tantalophile.demon.co.uk on Thu, Jun 21, 2001 at 06:07:01PM +0200
On Thu, Jun 21, 2001 at 06:07:01PM +0200, Jamie Lokier wrote:
> Pavel Machek wrote:
> > > Isn't this why noflushd exists or is this an evil thing that shouldn't
> > > ever be used and will eventually eat my disks for breakfast?
> >
> > It would eat your flash for breakfast. You know, flash memories have
> > no spinning parts, so there's nothing to spin down.
>
> Btw Pavel, does noflushd work with 2.4.4? The noflushd version 2.4 I
> tried said it couldn't find some kernel process (kflushd? I don't
> remember) and that I should use bdflush. The manual says that's
> appropriate for older kernels, but not 2.4.4 surely.
That's because of my favourite change from the 2.4.3 patch:
- strcpy(tsk->comm, "kupdate");
+ strcpy(tsk->comm, "kupdated");
noflushd 2.4 fixed this issue in the daemon itself, but I had forgotten about
the generic startup skript. (Rpms and debs run their customized versions.)
Either the current version from CVS, or
ed /your/init.d/location/noflushd << EOF
%s/kupdate/kupdated/g
w
q
EOF
should get you going.
Regards,
Daniel.
next prev parent reply other threads:[~2001-06-22 23:29 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 19:31 2.4.6-pre2, pre3 VM Behavior Tom Sightler
2001-06-13 20:21 ` Rik van Riel
2001-06-14 1:49 ` Tom Sightler
2001-06-14 3:16 ` Rik van Riel
2001-06-14 7:59 ` Laramie Leavitt
2001-06-14 9:24 ` Helge Hafting
2001-06-14 17:38 ` Mark Hahn
2001-06-15 8:27 ` Helge Hafting
2001-06-14 8:47 ` Daniel Phillips
2001-06-14 20:23 ` Roger Larsson
2001-06-15 6:04 ` Mike Galbraith
2001-06-14 20:39 ` John Stoffel
2001-06-14 20:51 ` Rik van Riel
2001-06-14 21:33 ` John Stoffel
2001-06-14 22:23 ` Rik van Riel
2001-06-15 15:23 ` spindown [was Re: 2.4.6-pre2, pre3 VM Behavior] Pavel Machek
2001-06-16 20:50 ` Daniel Phillips
2001-06-16 21:06 ` Rik van Riel
2001-06-16 21:25 ` Rik van Riel
2001-06-16 21:44 ` Daniel Phillips
2001-06-16 21:54 ` Rik van Riel
2001-06-17 10:28 ` Daniel Phillips
2001-06-17 10:05 ` Mike Galbraith
2001-06-17 12:49 ` (lkml)Re: " thunder7
2001-06-17 16:40 ` Mike Galbraith
2001-06-18 14:22 ` Daniel Phillips
2001-06-19 4:35 ` Mike Galbraith
2001-06-20 1:50 ` [RFC] Early flush (was: spindown) Daniel Phillips
2001-06-20 20:58 ` Tom Sightler
2001-06-20 22:09 ` Daniel Phillips
2001-06-24 3:20 ` Anuradha Ratnaweera
2001-06-24 11:14 ` Daniel Phillips
2001-06-24 15:06 ` Rik van Riel
2001-06-24 16:21 ` Daniel Phillips
2001-06-20 4:39 ` Richard Gooch
2001-06-20 14:29 ` Daniel Phillips
2001-06-20 16:12 ` Richard Gooch
2001-06-22 23:25 ` Daniel Kobras
2001-06-23 5:10 ` Daniel Phillips
2001-06-25 11:33 ` Pavel Machek
2001-06-25 11:31 ` Pavel Machek
2001-06-18 20:21 ` spindown Simon Huggins
2001-06-19 10:46 ` spindown Pavel Machek
2001-06-20 16:52 ` spindown Daniel Phillips
2001-06-20 17:32 ` spindown Rik van Riel
2001-06-20 18:00 ` spindown Daniel Phillips
2001-06-21 16:07 ` spindown Jamie Lokier
2001-06-22 22:09 ` Daniel Kobras [this message]
2001-06-28 0:27 ` spindown Troy Benjegerdes
2001-06-14 15:10 ` 2.4.6-pre2, pre3 VM Behavior John Stoffel
2001-06-14 18:25 ` Daniel Phillips
2001-06-14 8:30 ` Mike Galbraith
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=20010623000912.A415@pelks01.extern.uni-tuebingen.de \
--to=kobras@tat.physik.uni-tuebingen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=pavel@suse.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;
as well as URLs for NNTP newsgroup(s).