Re: Memory limits in Spice3f5 on Linux. (fwd)


To ng-spice-devel@ieee.ing.uniroma1.it
From Paolo Nenzi <pnenzi@ieee.ing.uniroma1.it>
Date Tue, 21 Dec 1999 17:18:10 +0100 (CET)
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
Reply-To ng-spice-devel@ieee.ing.uniroma1.it



---------- Forwarded message ----------
Date: Tue, 21 Dec 1999 17:15:48 +0100 (CET)
From: Paolo Nenzi <pnenzi@iol.it>
Reply-To: p.nenzi@ieee.org
To: pnenzi@ieee.ing.uniroma1.it
Subject: Re: Memory limits in Spice3f5 on Linux. (fwd)



---------- Forwarded message ----------
Date: Mon, 20 Dec 1999 18:15:22 +0100 (MET)
From: tuckey@ieee.org
To: p.nenzi@ieee.org
Subject: Re: Memory limits in Spice3f5 on Linux. (fwd)

Dear p.nenzi,

As promised, following is the email I received from Buzz Megg who claims
that the problem that I was facing was fixed about 2 years ago.  I have
forwarded the email for your interest.

Forwarded message:
> From buzmeg@hotmail.com  Fri Dec 17 19:35:16 1999
> X-UIDL: 682c5f4c92d733d7d448a813adc4d059
> Message-ID: <19991217183510.27653.qmail@hotmail.com>
> X-Originating-IP: [63.195.103.58]
> From: "Buzz Megg" <buzmeg@hotmail.com>
> To: tuckey@ieee.org
> Subject: Re: Memory limits in Spice3f5 on Linux.
> Date: Fri, 17 Dec 1999 13:35:10 EST
> Mime-Version: 1.0
> Content-Type: text/plain; format=flowed
> 
> Which patches for 3f5 have you applied?
> 
> This sounds like a really old (2 years+) memory bug.
> 
> I have just started recovery of some of my disks (damaged in a fire
> :( ) and should be able to extract a spice3f5 RPM I created which
> fixed a bunch of bugs with the @ command and added a new memory
> allocator.  It also applied every spice patch I could lay my hands
> on as well as bugs I fixed.
> 
> If you can't wait until about mid-January, I would suggest going
> into the spice3 code and shredding the memory management code.
> 
> Also, inside that memory management code is a macro called
> PAGESIZE or something like that and it's set to 4096 or something
> too small.  You might want to try making that much larger, when I
> used to work for DEC we needed to really make that big or would
> see weird memory problems.  I don't understand the reasoning, however.
> 
> Also, when you start seeing memory allocation errors, you need
> to include the architecture of your box (Intel, Alpha/AXP, Sparc,
> etc.) as each one has it's own way of dealing with memory allocation.
> 
> -Andy
> 
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
> 


-- 
Andrew Tuckey
Postdoctoral Research Scientist
Eindhoven University of Technology
EE Dept., Group EMV,  Room EL 1.13
PO Box 513                        Phone: +31 - 40 2 47 3895
5600 MB EINDHOVEN                 Fax:   +31 - 40 2 43 4364
The Netherlands.                  Email: Tuckey@ieee.org


Partial thread listing: