mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Balbir" <balbir@ti.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Disabling file system caching
Date: Mon, 20 Jan 2003 13:17:42 +0530	[thread overview]
Message-ID: <006f01c2c058$3748ad00$6353579d@india.ti.com> (raw)

Not sure if posting to the newsgroup linux.kernel sends
it to the mailing list too.

"Balbir Singh" <balbir_soni@yahoo.com> wrote in message
news:b0g6q2$lfq$1@tilde.itg.ti.com...
> "Rik van Riel" <riel@conectiva.com.br> wrote in message
> news:20030120011009$2d98@gated-at.bofh.it...
> > On Sun, 19 Jan 2003, Jean-Eric Cuendet wrote:
> >
> > > Is it possible to disable file caching for a given partition or mount?
> >
> > No, if you do that mmap(), read(), write() etc. would be impossible.
> >
> > > Or at least to limit it at a certain quantity of memory?
> >
> > Not yet.  I'm thinking of implementing something like this
> > for the next version of -rmap (reclaim only from the cache
> > if the cache occupies more than a certain fraction of ram).
>

I think that this feature is very important. In an embedded system
using an NFS root filesystem, we found that the file cache
would take a lot of memory and all insmods would fail. This is
especially true when the system boots up and looks for /lib/modules.

I think it should be possible to modify the slab allocator to
implement a memory pool. We could add a flag which would prevent
the slab from growing beyond its initial size.

This approach would work only if the cache is allocated by
using the slab allocator.

Balbir




             reply	other threads:[~2003-01-20  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20  7:47 Balbir [this message]
2003-01-20 14:21 ` Jan Hudec
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20 12:52 Martin Knoblauch
2003-01-19 17:05 Jean-Eric Cuendet
2003-01-20  1:05 ` Rik van Riel
2003-01-20 19:47   ` Folkert van Heusden
2003-01-20 21:39     ` Nuno Silva

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='006f01c2c058$3748ad00$6353579d@india.ti.com' \
    --to=balbir@ti.com \
    --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

Powered by JetHome