From: "Chuck Lever" <cel@netapp.com>
To: linux-mm@kvack.org
Subject: RE: vm_enough_memory() and RAM disks
Date: Tue, 22 May 2001 21:32:33 -0400 [thread overview]
Message-ID: <NFBBLKEIKLGDCJAAAEKOKEDPCAAA.cel@netapp.com> (raw)
In-Reply-To: <3B0ACB08.C9032ADB@mvista.com>
i've noticed a (possibly) related problem.
i've configured an NFS server to export a largish RAM disk for
the purposes of testing NFS performance. the RAM disk is half
as large as the server's physical memory. i've seen several
times that when the machine runs out of memory (the "free"
column in vmstat output goes below 1M) and the kernel wants
to swap, the system freezes up. my theory was that something
was attempting to flush buffers, but because the buffers were
bh_protected (because they were part of a large RAM disk), the
kernel wasn't successful at making any normal headway, and so
it looped.
> -----Original Message-----
> From: owner-linux-mm@kvack.org [mailto:owner-linux-mm@kvack.org]On
> Behalf Of Scott Anderson
> Sent: Tuesday, May 22, 2001 4:25 PM
> To: linux-mm@kvack.org
> Subject: vm_enough_memory() and RAM disks
>
>
> I've noticed that vm_enough_memory() does not account for the
> fact that buffer cache could be used for RAM disks. It appears that it
> assumes that all of buffer cache is only being used for caching data
> from disk drives and could be freed up as needed. Logically, I think
> what needs to happen is that the amount of space occupied by buffers
> with BH_Protected needs to be subtracted off of buffermem_pages.
>
> As you can well imagine, in small systems with relatively large RAM
> disks, this does not lead to good behavior...
>
> Now for the true confession: I'm not finding time to come up with a
> patch for this right now. However, I thought it would be better to at
> least get this out instead of waiting around for me to find the time.
>
> Thanks for listening,
> Scott Anderson
> scott_anderson@mvista.com MontaVista Software Inc.
> (408)328-9214 1237 East Arques Ave.
> http://www.mvista.com Sunnyvale, CA 94085
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux.eu.org/Linux-MM/
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-23 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 20:24 Scott Anderson
2001-05-23 1:32 ` Chuck Lever [this message]
2001-05-23 17:45 ` Scott Anderson
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=NFBBLKEIKLGDCJAAAEKOKEDPCAAA.cel@netapp.com \
--to=cel@netapp.com \
--cc=linux-mm@kvack.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