From: Pablo Borges <pablo.borges@uol.com.br>
To: Helge Hafting <helgehaf@idb.hist.no>
Cc: war@starband.net, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.16 & Heavy I/O
Date: Wed, 5 Dec 2001 17:57:41 -0200 [thread overview]
Message-ID: <20011205175741.124caeff.pablo.borges@uol.com.br> (raw)
In-Reply-To: <3C0790A4.4009C357@idb.hist.no>
In-Reply-To: <B7F1F9B7DE30EDF47ADB4F8F44CAC84B@war.starband.net> <3C0790A4.4009C357@idb.hist.no>
On Fri, 30 Nov 2001 14:59:00 +0100
Helge Hafting <helgehaf@idb.hist.no> wrote:
> Absolutely all free memory may be used for disk caching. So
> no, you can't get a bigger cache because it is already at
> the highest possible setting. You don't have more memory
> for this - all is used already.
May I limit this memory ? For a long time I'm working all day with no physical memory available.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pablo Borges pablo.borges@uol.com.br
-------------------------------------------------------------------
____ Tecnologia UOL
/ \ Debian:
| =_/ The 100% suck free linux distro.
\
\ SETI is lame. http://www.distributed.net
Dnetc is XNUG!
next prev parent reply other threads:[~2001-12-05 19:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:46 Kernel 2.4.16 & Heavy I/O war war
2001-11-29 15:43 ` Blue Lang
2001-11-29 18:01 ` Andrew Morton
2001-11-29 21:42 ` Martin Josefsson
2001-11-30 13:59 ` Helge Hafting
2001-12-05 19:57 ` Pablo Borges [this message]
2001-12-05 20:07 ` Roy Sigurd Karlsbakk
2001-12-06 18:06 ` Pablo Borges
2001-12-06 18:10 ` Roy Sigurd Karlsbakk
2001-12-06 18:28 ` Pablo Borges
2001-12-06 18:38 ` Rik van Riel
2001-12-06 19:36 ` Mike Galbraith
2001-12-06 19:56 ` Rik van Riel
2001-12-06 22:50 ` Alan Cox
2001-12-07 5:37 ` Mike Galbraith
2001-12-07 8:43 ` Alan Cox
2001-12-07 21:53 ` Mike Galbraith
2001-12-07 22:02 ` Rik van Riel
2001-12-07 13:46 ` Stephan von Krawczynski
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=20011205175741.124caeff.pablo.borges@uol.com.br \
--to=pablo.borges@uol.com.br \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=war@starband.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.