From: Jan Hudec <bulb@ucw.cz>
To: Ewerton Romulo <ewertonromulo@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Run linux in ramdisk(tmpfs) and use a mounted HD for files cause memory and CPU overflow!
Date: Wed, 29 Jun 2005 10:41:29 +0200 [thread overview]
Message-ID: <20050629084129.GA5701@vagabond> (raw)
In-Reply-To: <1f52e8ed05062821415f505fee@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On Wed, Jun 29, 2005 at 01:41:13 -0300, Ewerton Romulo wrote:
> OK!
>
> /proc/modules
> [snipped]
Only network stuff here. Since there is no problem when disk is not
used, I think we can rule out network stuff.
> My /proc/mount is:
> rootfs / rootfs rw 0 0
> /dev/root / tmpfs rw 0 0
So you are using tmpfs, *not* ramdisk. Tmpfs lives in memory and
occupies amout of memory equal to amount of data stored. Unlike ramdisk,
memory is reclaimed when you remove files from tmpfs and when you umount
it.
> /proc /proc proc rw 0 0
> devpts /dev/pts devpts rw 0 0
> /dev/hda1 /test vfat rw 0 0
Ok, got the picture.
> I use kernel 2.4.30 oficial, no especific linux distribution!
You should have included your config too, since you are using a custom
one. We need to know what drivers you have compiled in your kernel. It's
called .config and located in the build directory of the kernel.
And of course, you did not include the most important stuff --
/proc/meminfo, /proc/slabinfo, /proc/diskstats and /proc/vmstats from
time when it exhibits the problem. Also you forgot about /proc/swaps (it
may be empty or not even exist, but you should at least say so).
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-29 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 9:18 Run linux in ramdisk(tmpfs) and use a mounted HD for files cause memory and CPU overflow! Ewerton Romulo
2005-06-27 14:20 ` Jan Hudec
2005-06-28 18:06 ` Ewerton Romulo
2005-06-28 20:24 ` Jan Hudec
2005-06-29 4:41 ` Ewerton Romulo
2005-06-29 8:41 ` Jan Hudec [this message]
2005-06-29 16:28 ` Bryan Henderson
2005-06-29 18:36 ` Ewerton Romulo
2005-06-29 21:00 ` Bryan Henderson
2005-06-30 16:02 ` Jan Hudec
2005-06-29 18:46 ` Ewerton Romulo
2005-06-28 21:42 ` Bryan Henderson
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=20050629084129.GA5701@vagabond \
--to=bulb@ucw.cz \
--cc=ewertonromulo@gmail.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).