[okl4-developer] out of vmalloc space

[Geoffrey Lee]

On Mon, Nov 24, 2008 at 03:43:30PM +0900, 최수길 wrote:
> I looked at Linux SConscript to increase the memory given to the linux.
>  
> But I could not figure it out.
>  
> Please tell me the way in more detail.


You can change the heap size by setting the heap = in the 
SConscript.

	-gl

>  
> Thanks.
>  
> -----Original Message-----
> From: "Geoffrey Lee"<glee at ok-labs.com> 
> To: "최수길"<hips05 at naver.com>
> Cc: 
> Sent: 08-11-18(화) 18:06:17
> Subject: Re: Re: [okl4-developer] out of vmalloc space
> On Tue, Nov 18, 2008 at 05:54:48PM +0900, 최수길 wrote:
> > Initially, the size of vmalloc space was 0x400000.
> Would it be possible for you to tell us exactly what drivers /
> modifications you made as well as what your program
> is trying to do? Normally user programs 
> don't invoke the vmalloc routines, this makes me think
> you are doing more than just running a program. In particular,
> I think your program is causing some device driver which you 
> enabled to try to allocate a large block of kernel virtual
> memory. In OK Linux, the vmalloc memory is pre-backed 
> with physical memory rather than faulted in on demand, 
> this probably explains your out of memory situation as
> all your memory was probably used to back your large 
> vmalloc section.
> The memory given to OK Linux by default is 20M, you can
> increase that in the Linux SConscript.
> -gl
> p.s. Please post on-list. There are other OKL4 developers who are
> on this list who might also be able to help you.
> > 
> > For simplicity, let's call the program which causes the error of "out of vmalloc space" prog_A.
> > 
> > With the vmalloc space of 0x400000 size, prog_A was executed without problem.
> > 
> > After adding some device drivers and servers, I encountered the error by executing the prog_A.
> > 
> > Before executing the prog_A, everything was OK.
> > 
> > I increased the size of vmalloc space up to 0xe00000, but the problem was not solved.
> > 
> > As it was all right with the vmalloc space of 0x400000, I thought the problem would be solved
> > by adding less than 0x400000.
> > 
> > But, it was not.
> > 
> > If I increase the size of vmalloc space up to 0xf00000, I see an error as below.
> > 
> > I always appreciate your help.
> > 
> > Thanks.

> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer


--