Re: mmap()

2005-11-24 Thread Joseph Koshy
ata .text >start of text< (gap) Virtual address 0 Possible solutions could be: - link statically (i.e., don't fragment the mmap arena) - reduce the data segment size (i.e., reduce the malloc arena size) by tweaking the run time limits associated with the process. -- FreeBSD V

Re: mmap()

2005-11-24 Thread Michael Conlen
On Nov 23, 2005, at 5:21 PM, Robert Watson wrote: On Wed, 23 Nov 2005, Michael Conlen wrote: Sorry if this is the wrong place for this, but I haven't been getting answers elsewhere. I'm trying to tune the system to allow very large mmap()'s in a single process space, s

Re: mmap()

2005-11-23 Thread Robert Watson
On Wed, 23 Nov 2005, Michael Conlen wrote: Sorry if this is the wrong place for this, but I haven't been getting answers elsewhere. I'm trying to tune the system to allow very large mmap()'s in a single process space, something on the order of 1.5 GB so I can pass very la

Re: mmap()

2005-11-23 Thread Nikos Ntarmos
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there. What is the value of vm.max_proc_mmap? Also, what is the value of KVA_PAGES in your kernel config? \n\n -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Nikos Ntarmos <[EMAIL PROTECTED]> iD8DBQFDhNVCm6J1ac+VFgoRAhLJAJ

Re: mmap()

2005-11-23 Thread Michael Conlen
it cputime unlimited filesize unlimited datasize 524288 kbytes stacksize65536 kbytes coredumpsize unlimited memoryuseunlimited vmemoryuse unlimited descriptors 6861 memorylocked unlimited maxproc 3430 sbsize unlimited c++ -o mmap mmap.c ./mmap 757254143 sz2d

Re: mmap()

2005-11-23 Thread W�rner
> limit > > cputime unlimited > > filesize unlimited > > datasize 524288 kbytes > > stacksize65536 kbytes > > coredumpsize unlimited > > memoryuseunlimited > > vmemoryuse unlimited > > descriptors 6861 > > memorylocked

Re: mmap()

2005-11-23 Thread Michael Conlen
On Nov 23, 2005, at 1:20 PM, Arne Wörner wrote: --- Michael Conlen <[EMAIL PROTECTED]> wrote: On Nov 23, 2005, at 12:11 PM, Arne Wörner wrote: --- Michael Conlen <[EMAIL PROTECTED]> wrote: I'm trying to tune the system to allow very large mmap()'s in a I had a simil

Re: mmap()

2005-11-23 Thread W�rner
--- Michael Conlen <[EMAIL PROTECTED]> wrote: > On Nov 23, 2005, at 12:11 PM, Arne Wörner wrote: > > --- Michael Conlen <[EMAIL PROTECTED]> wrote: > >> I'm trying to tune the system to allow very large > >> mmap()'s in a > >> > >

Re: mmap()

2005-11-23 Thread ender
Arne Wörner wrote: --- Michael Conlen <[EMAIL PROTECTED]> wrote: I'm trying to tune the system to allow very large mmap()'s in a I had a similar problem with shared memory. I found an option in /sys/conf/NOTES. I think it could help in your case, if u increase %

Re: mmap()

2005-11-23 Thread Michael Conlen
On Nov 23, 2005, at 12:11 PM, Arne Wörner wrote: --- Michael Conlen <[EMAIL PROTECTED]> wrote: I'm trying to tune the system to allow very large mmap()'s in a I had a similar problem with shared memory. I found an option in /sys/conf/NOTES. I think it could help in

Re: mmap()

2005-11-23 Thread W�rner
--- Michael Conlen <[EMAIL PROTECTED]> wrote: > I'm trying to tune the system to allow very large > mmap()'s in a > I had a similar problem with shared memory. I found an option in /sys/conf/NOTES. I think it could help in your case, if u increase % options

mmap()

2005-11-23 Thread Michael Conlen
Sorry if this is the wrong place for this, but I haven't been getting answers elsewhere. I'm trying to tune the system to allow very large mmap()'s in a single process space, something on the order of 1.5 GB so I can pass very large values for -Xms and -Xmx to java. I know