Hi.
Great. After some tries 2.9GB was the maximum that it works
with. Ok with me.
--RESOLVED--
About 'dfldsiz' - I meant that I've set it in /boot/loader.conf
via 'su -' , and rebooted the machine. It didn't influenced.
(It was the first try today, may be I did something wrong, though.)
But the
On Mar 12, 2007, at 12:02 PM, Dima Sorkin wrote:
Something is probably wrong.
kern.dfldsiz on my machine does not influence.
I don't believe you can change that value after the system has
booted-- you have to set it either in the kernel's config file, or
in /boot/loader.conf, for this to ac
Hi.
Something is probably wrong.
kern.dfldsiz on my machine does not influence.
I.e. after booting I run
$ limits
and it shows me the old 500M.
Now, a point about 'maxdsiz'= 3.0-3.5G instead of 4G - this one I must check.
I tried 3.9G :)
Thanks,
Dima.
On 3/12/07, Chuck Swiger wrote:
It is c
On Mar 12, 2007, at 11:20 AM, Dima Sorkin wrote:
2) 'maxdsiz' - Yes, as long as I keep 'maxdsiz + maxssiz' below
physical
memory size - everything is fine. Single process allocates
successfully
up to 'maxdsiz'.
When tried to put 'maxdsiz' > phys mem size,
indeed t
Hi.
I experimented with the values:
1) On my machine 'maxusers' doesn't influence the maximum memory
allowable for allocation for single process.
2) 'maxdsiz' - Yes, as long as I keep 'maxdsiz + maxssiz' below physical
memory size - everything is fine. Single process allocates successfu
Dima Sorkin wrote:
> Hi.
> I've read some pages about 'kern.maxusers', 'kern.maxdsize'.
> I have questions:
> 1)
> After I reduce 'maxusers' to some reasonable amount for that computer
> (say 10),
maxusers is somewhat badly named because of historical reasons. Today it
means something like "how ma
Hi.
I've read some pages about 'kern.maxusers', 'kern.maxdsize'.
I have questions:
1)
After I reduce 'maxusers' to some reasonable amount for that computer (say 10),
and enlarge 'maxdsize', will a user process be able to allocate
arrays that are considerably bigger than the physical memory size ?
Dima,
Not all the settings there are tuneable. In 6.X the allowable memory is
somewhat automatic based on the max users. Your kernel is set to 384. You
can try changing that.
You can also make some kernel settings in:
/boot/loader.conf
You can see the possible variables to set in:
/boot/d
Dima Sorkin wrote:
> Hi.
>
> On FreeBSD 6.2 i386 with 2GB of physical memory I can't allocate
> more than 500Mb for my program.
>
> I'm a new to FreeBSD. Is this limitatin is something known,
> how do I overcome it ?
Google for MAXDSIZ and relevent discussions.
See here for example:
http://list
check out your sysctl values.
man sysctl
for more information.
-Derek
At 08:32 AM 3/9/2007, Dima Sorkin wrote:
Hi.
On FreeBSD 6.2 i386 with 2GB of physical memory I can't allocate
more than 500Mb for my program.
I'm a new to FreeBSD. Is this limitatin is something known,
how do I ove
Hi.
On FreeBSD 6.2 i386 with 2GB of physical memory I can't allocate
more than 500Mb for my program.
I'm a new to FreeBSD. Is this limitatin is something known,
how do I overcome it ?
(On linuxes I can allocate arrays of size close to sum
of physical and swap memory, on similar machines)
Thank
11 matches
Mail list logo
