From: ebiederm@inetnebr.com (Eric W. Biederman)
To: lonnie@valemount.com
Cc: linux-mm@kvack.org
Subject: Re: memory use in Linux
Date: 21 Aug 1998 18:48:22 -0500 [thread overview]
Message-ID: <m1iujlj3qx.fsf@flinx.npwt.net> (raw)
In-Reply-To: Lonnie Nunweiler's message of Thu, 20 Aug 1998 22:37:33 -0700
>>>>> "LN" == Lonnie Nunweiler <lonnie@valemount.com> writes:
LN> I am researching why Linux runs into memory problems. We recently had to
LN> convert our dialin server, email and web server to NT, because the Linux
LN> machine would eventually eat up all ram, and then crash. We were using
LN> 128MB machines, and it would take about 3 days before rebooting was
LN> required. If we didn't reboot soon enough, it was a very messy job
LN> rebuilding some of the chewed files.
Instead of running into generalities probably the best place to start is
to ask why linux ran into problems in your case.
Which kernel were you running?
What were the specifics that killed your machine?
Did it look like a kernel memory where more and more memory is eaten,
your machine begins to swap harder, and harder until death.
Or was it a user space program that leaked memory, and linux wasn't
able to cope with runing out of swap?
The cache in general is designed so anything it caches may be
reclaimed when needed.
I think you are barking up the wrong tree so please take it slow
so the real culprit can be found.
Eric
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-08-21 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-21 5:37 Lonnie Nunweiler
1998-08-21 6:20 ` Adam Fritzler
1998-08-21 23:48 ` Eric W. Biederman [this message]
1998-08-24 10:36 ` Stephen C. Tweedie
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=m1iujlj3qx.fsf@flinx.npwt.net \
--to=ebiederm@inetnebr.com \
--cc=linux-mm@kvack.org \
--cc=lonnie@valemount.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