mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: skraw@ithnet.com (Stephan von Krawczynski)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	mcelrath@draal.physics.wisc.edu, linux-kernel@vger.kernel.org
Subject: Re: "Cached" grows and grows and grows...
Date: Sat, 8 Sep 2001 18:14:46 +0100 (BST)	[thread overview]
Message-ID: <E15flgs-0004BN-00@the-village.bc.nu> (raw)
In-Reply-To: <20010908184758.696bb9d1.skraw@ithnet.com> from "Stephan von Krawczynski" at Sep 08, 2001 06:47:58 PM

> //      printk(KERN_ERR "__alloc_pages: %lu-order allocation failed.\n", order)
>         return NULL;
> 
> If there is no printk, you will obviously not notice the problem. You can bet
> your car on not "seeing the problem".

That printk is commented out because its pointless and bogus noise. It just
causes confused bug reporting. The stuff that matters is cache sizes
shrinking back when we need memory not slowly eating the computer alive.

> Nevertheless there _is_ a problem, because nfs still fails on low mem situation
> when option "no_subtree_check" is _off_/not used.

In certain cases NFS will struggle. It isnt as bad in -ac as we use
GFP_KERNEL for nfs level reassembly. It happens in 2.2 as well tho.

Alan

  reply	other threads:[~2001-09-08 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07 16:08 Bob McElrath
2001-09-07 17:13 ` Stephan von Krawczynski
2001-09-07 22:15   ` Alan Cox
2001-09-07 22:24     ` Bob McElrath
2001-09-08  0:53     ` VM improvement in -ac [was: "Cached" grows and grows and grows...] Mike Fedyk
2001-09-08 16:47   ` "Cached" grows and grows and grows Stephan von Krawczynski
2001-09-08 17:14     ` Alan Cox [this message]
2001-09-09 13:15     ` Stephan von Krawczynski
2001-09-09 13:34       ` Alan Cox
2001-09-26  1:55 M. Edward Borasky

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=E15flgs-0004BN-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcelrath@draal.physics.wisc.edu \
    --cc=skraw@ithnet.com \
    /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®