public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Zeng Yu <yu_zeng@263.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Ramdisk Bug?
Date: Wed, 27 Jun 2001 16:59:45 +0200	[thread overview]
Message-ID: <20010627165945.A16936@athlon.random> (raw)
In-Reply-To: <001e01c0ff14$0bdc7540$0101a8c0@weqeqe>
In-Reply-To: <001e01c0ff14$0bdc7540$0101a8c0@weqeqe>; from yu_zeng@263.net on Wed, Jun 27, 2001 at 10:18:26PM +0800

On Wed, Jun 27, 2001 at 10:18:26PM +0800, Zeng Yu wrote:
> Hi all,
> 
> I think find a ramdisk bug of 2.4.4 kernel -- ramdisk
> use both buffers and cached mem of the same size, thus
> double the mem use. 
> mke2fs -m0 /dev/ram1
> mount /dev/ram1 /mnt
> dd if=/dev/zero of=/mnt/data bs=1k count=110000
> cat /proc/meminfo will see that both buffers and
> cached mem increase about 110M of size. More worse,
> the cached mem won't be released untile the ramdisk
> be umounted. I attach the meminfo and slabinfo before

the "more worse" part is the only thing which is wrong. The fact cache
also grows to 110M is expected and it won't change. With the
blkdev-pagecache patch the cache will grow to 220M and it will shrink to
110M if you are low on memory (buffer cache will only be allocated for
the superblock and inode metadata with ext2).

use ramfs if you want zero ram duplication and you don't care about the
physical representation on disk of your data in cache.

> and after data transfer below.

Try this patch to fix the "more worst part"  (beware totally untested).

--- blkdev-rd/include/linux/swap.h.~1~	Sun Jun 24 02:06:13 2001
+++ blkdev-rd/include/linux/swap.h	Wed Jun 27 16:47:57 2001
@@ -274,7 +274,7 @@
 #endif
 
 #define page_ramdisk(page) \
-	(page->buffers && (MAJOR(page->buffers->b_dev) == RAMDISK_MAJOR))
+	(!page->mapping && page->buffers && (MAJOR(page->buffers->b_dev) == RAMDISK_MAJOR))
 
 extern spinlock_t swaplock;
 

Andrea

  reply	other threads:[~2001-06-27 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27 14:18 Ramdisk Bug? Zeng Yu
2001-06-27 14:59 ` Andrea Arcangeli [this message]
2001-06-28 14:21   ` Zeng Yu

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=20010627165945.A16936@athlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yu_zeng@263.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