Date: Thu, 10 Oct 2002 15:23:19 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Robert Watson <rwatson@freebsd.org> Cc: Ben Stuyts <ben@stuyts.nl>, current@freebsd.org Subject: Re: Again: panic kmem_malloc() Message-ID: <3DA5FDD7.83D3C725@mindspring.com> References: <Pine.NEB.3.96L.1021010175350.39392C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > I've run into this on a couple of boxes, but those boxes were diskless > root boxes, and used md backed ffs for /tmp and /var. Apparently if you > do that, you're likely to exceed the kernel's auto-tuned kmem map size. > That said, they didn't do it as frequently, so perhaps there's been a > chance. A glance at the malloc buckets on the machine suggested that this > wasn't a memory leak (the normal candidate in this sort of scenario). Use of swapping on additional space not known to the kernel at boot time, will also cause this; the auto-sizing of the map can only know about the things it knows about, so adding more later with consume the available KVA space, without growing it (all physical memory and all swap is assumed to have mappings allocated since the mappings need to be filled in at fault time. It's very tempting to seperate the mapping allocations; this would be a pretty big chore. 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DA5FDD7.83D3C725>