amd64/145654: amd64-curent memory leak in kernel

Andriy Gapon avg at freebsd.org
Mon Dec 6 16:20:14 UTC 2010


The following reply was made to PR amd64/145654; it has been noted by GNATS.

From: Andriy Gapon <avg at freebsd.org>
To: Andrey Smagin <samspeed at mail.ru>, bug-followup at freebsd.org
Cc:  
Subject: Re: amd64/145654: amd64-curent memory leak in kernel
Date: Mon, 06 Dec 2010 18:16:30 +0200

 on 05/12/2010 22:47 Andrey Smagin said the following:
 >> Is still reproducible?
 >> How much RAM do you have?  What panic message is printed when this happens?
 >> This could be a KVA exhaustion or fragmentation issue related to ZFS.
 > 
 > I have 4G of RAM, panic messages about malloc memory for network subsystem.
 > After opening PR was some commit helped decrease memory usage under heavy
 > load. I use last night CURRENT right now. Next loader.conf now avoiding this problem:
 > 
 > vfs.zfs.arc_max="300M"  - larger size increase performance but also increase possibility of panic
 
 So you can still reproduce the panic with CURRENT?
 Can you get panic message and stack trace?
 
 > vfs.zfs.vdev.cache.size="16M"
 > vfs.zfs.cache_flush_disable="0"
 > vfs.zfs.prefetch_disable="0"
 >  
 > vfs.zfs.zfetch.array_rd_sz="4M"
 > vfs.zfs.zfetch.block_cap="256"
 > vfs.zfs.zfetch.min_sec_reap="2"
 > vfs.zfs.zfetch.max_streams="16"
 > 
 > vm.kmem_size="4G"
 > 
 > IMHO gigantic problem is -  ZFS use "wired" memory instead "inactive" as UFS.
 
 That's the way ZFS is.
 
 -- 
 Andriy Gapon


More information about the freebsd-net mailing list