From: Andreas Dilger <adilger@clusterfs.com>
To: "Jürgen Scholz" <juergen@scholz-gmbh.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hude read/write cache
Date: Wed, 14 Jan 2004 13:15:07 -0700 [thread overview]
Message-ID: <20040114201507.GE1964@schnapps.adilger.int> (raw)
In-Reply-To: <BC2B59C1.2E87%juergen@scholz-gmbh.cc>
On Jan 14, 2004 20:40 +0100, Jürgen Scholz wrote:
> I got a small server, which main purpose is routing and dialup besides being
> a repository for files. This system is very noisy. Because of that I want to
> stop the disks from spinning, when the system is in regular usage (standby,
> routing..). This should happen through a read and write cache which keeps
> the most often used files in RAM (like log files, bash, ...), so that there
> is no need for the system to access the (physical) hard drive.
> I would like to use a regular filesystem with a sort of transparent cache.
> Any ideas?
Look for the laptop-mode patches, they do exactly this.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2004-01-14 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 19:40 Hude read/write cache Jürgen Scholz
2004-01-14 20:15 ` Andreas Dilger [this message]
2004-01-14 22:07 ` Bart Samwel
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=20040114201507.GE1964@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=juergen@scholz-gmbh.cc \
--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