From: Rik van Riel <riel@conectiva.com.br>
To: Eric Whiting <ewhiting@amis.com>
Cc: linux-mm@kvack.org
Subject: Re: large mem, heavy paging issues (256M VmStk on Athlon)
Date: Fri, 23 Feb 2001 21:38:11 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.31.0102232136210.8568-100000@localhost.localdomain> (raw)
In-Reply-To: <3A96C430.C028E954@amis.com>
On Fri, 23 Feb 2001, Eric Whiting wrote:
> Thanks for the info -- but I'm not sure I understand what the fix is
> to be. Does my lisp engine need to be recompiled with a newer glibc?
> Do I need to change something else?
If your lisp engine is dynamically linked to glibc, a simple
glibc upgrade should do the trick (if this thing is fixed in
newer glibcs).
> I think the strace showed the process is using mainly malloc (mmap)
> for memory allocation. I do see some brk() calls at the first. (these
> appear to be returning a 2G number not a 1G number like you suggested)
> brk(0x805a000) = 0x805a000
Actually, this would be 0x0805a000 if you wrote out the leading
0 ... this is more like 128 MB ;)
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com.br/
--
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-02-24 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 0:39 Eric Whiting
2001-02-21 22:39 ` Rik van Riel
2001-02-23 20:12 ` Eric Whiting
2001-02-24 2:38 ` Rik van Riel [this message]
2001-02-24 3:15 ` Eric Whiting
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=Pine.LNX.4.31.0102232136210.8568-100000@localhost.localdomain \
--to=riel@conectiva.com.br \
--cc=ewhiting@amis.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