Date: Sun, 30 Dec 2001 23:28:56 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Anjali Kulkarni" <anjali@indranetworks.com> Cc: <osa@freebsd.org.ru>, <freebsd-hackers@FreeBSD.ORG> Subject: Re: Kernel Memory Limit Message-ID: <200112310728.fBV7SuQ19094@apollo.backplane.com> References: <006e01c1905f$25fd1380$0a00a8c0@indranet> <20011229164322.A73212@freebsd.org.ru> <002801c191c2$9c497fb0$0a00a8c0@indranet>
next in thread | previous in thread | raw e-mail | index | archive | help
:Hi,
:
:I have tried this too, it makes absoutely no difference at all. My mallocs
:fail after a certain no. of runs of my code(and there is no memory leak),
:and there was no difference by increasing MAXDSIZ/DFLDSIZ.
:
:Thanks,
:Anjali
MAXDSIZ and DFLDSIZ are associated with USER malloc()s, not
kernel malloc()s.
If you are trying to use malloc() in kernel code there are some
rather severe limits. 'vmstat -m' will give you a rundown on the
statistics.
KVM is only 1G, and a lot of is used-up. You cannot allocate
(directly map) hundreds of megabytes of kernel memory.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112310728.fBV7SuQ19094>