The ulimits will ultimately be capped by the platform MAXDSIZ, which
for mipses probably is 1G:

./arch/mips64/include/vmparam.h:#define MAXDSIZ
(1*1024*1024*1024)      /* max data size */

..so that's where "ulimit -d unlimited" will allow at most.

2012/6/15 Rafael Sadowski <raf...@sizeofvoid.org>:
> On Thu Jun 14, 2012 at 10:20:52AM -0700, Bryan Irvine wrote:
>> On Thu, Jun 14, 2012 at 6:13 AM, Rafael Sadowski <raf...@sizeofvoid.org>
>> wrote:
>> >
>> > Do you see "VMEM_WARNING=Yes?
>> >
>> > Cheers, Rafael
>>
>> I did.  I increased the limit though they appear to already be at max
>> values.  When watching top during the compile it never gets to a point
>> where it needs to swap.
>>
>> This is what top shows right before it dies:
>> Memory: Real: 210M/339M act/tot Free: 671M Cache: 674M Swap: 0k/1280M
>
> OK, but you need to check 'ulimit -d'. Please, test built with:
> "ulimit -d unlimited". I have no experiences with lemote and I don't
> know the limits.
>
> Cheers, Rafael
>



--
 To our sweethearts and wives.  May they never meet. -- 19th century toast

Reply via email to