From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel hangs in 118th call to vmalloc
Date: Fri, 31 Aug 2001 15:41:21 -0500 [thread overview]
Message-ID: <3B8FF671.1050804@interactivesi.com> (raw)
In-Reply-To: <E15cv3e-0003vf-00@the-village.bc.nu>
Alan Cox wrote:
> vmalloc shouldnt be hanging the box, although in 2.4.2 the out of memory
> handling is not too reliable. You have to understand vmalloc isnt meant to
> be used that way and the kernel gets priority over user space for allocs so
> is able to get itself to the point it killed off all user space.
So you're saying it's a bug that I can't work around?
It's probably a moot point. I've come up with a different algorithm
that allocates all but 32MB of RAM, and it appears to work well.
I heard that 2.4.9 doesn't even run "thrash". Is this true? If so, why
are these buggy VM's being released in the first place?
next prev parent reply other threads:[~2001-08-31 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 18:40 kernel hangs in 118th call to vmalloc Timur Tabi
2001-08-31 20:38 ` Alan Cox
2001-08-31 20:41 ` Timur Tabi [this message]
2001-08-31 20:54 ` Alan Cox
2001-09-08 18:30 ` Eric W. Biederman
2001-09-08 19:39 ` Timur Tabi
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=3B8FF671.1050804@interactivesi.com \
--to=ttabi@interactivesi.com \
--cc=linux-kernel@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