mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pablo Borges <pablo.borges@uol.com.br>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.16 & Heavy I/O
Date: Thu, 6 Dec 2001 16:06:30 -0200	[thread overview]
Message-ID: <20011206160630.1f4ab058.pablo.borges@uol.com.br> (raw)
In-Reply-To: <Pine.LNX.4.30.0112052106450.3740-100000@mustard.heime.net>
In-Reply-To: <20011205175741.124caeff.pablo.borges@uol.com.br> <Pine.LNX.4.30.0112052106450.3740-100000@mustard.heime.net>


Don't we have a "dont't eat my whole memory, disk cache" option on linux ?


On Wed, 5 Dec 2001 21:07:42 +0100 (CET)
Roy Sigurd Karlsbakk <roy@karlsbakk.net> 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.
> 
> You can try rtlinux. In rtlinux (realtime linux), you tell linux how
> much memory the kernel will have access to, and let specially written
> apps to take the rest
> --
> Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
> 
> Computers are like air conditioners.
> They stop working when you open Windows.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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!


  parent reply	other threads:[~2001-12-06 18:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 15:46 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
2001-12-05 20:07   ` Roy Sigurd Karlsbakk
2001-12-06 18:06   ` Pablo Borges [this message]
2001-12-06 18:10     ` Roy Sigurd Karlsbakk
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-06 18:28     ` Pablo Borges
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=20011206160630.1f4ab058.pablo.borges@uol.com.br \
    --to=pablo.borges@uol.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®