hammer-inodes: malloc limit exceeded

[YONETANI Tomokazu]

On Tue, Oct 21, 2008 at 09:35:33AM -0700, Matthew Dillon wrote:
> 
> :The machine performed a pkgsrc "cvs update" before it crashed.  If more
> :information is needed, I'll provide it.  After the reboot kern.maxvnodes
> :is 129055 if that matters ...
> :
> :Regards
> :
> :	Matthias
> 
>     It's the same issue.  Drop kern.maxvnodes to 100000.
> 
>     I am going to add an API to set the kmalloc pool's limit so HAMMER
>     can size it according to the size of hammer_inode.

Do I still need to lower kern.maxvnodes to avoid the panic on machine
with >=2G bytes of RAM?  I still see this panic while running blogbench
for a couple of hours, without increasing or decreasing kern.maxvnodes.

  (kgdb) bt
	:
  #2  0xc0198e0c in panic (fmt=0xc02e71dd "%s: malloc limit exceeded")
      at /home/source/dragonfly/current/src/sys/kern/kern_shutdown.c:800
  #3  0xc0196a4f in kmalloc (size=584, type=0xc4170010, flags=258)
      at /home/source/dragonfly/current/src/sys/kern/kern_slaballoc.c:490
  #4  0xc0260056 in hammer_get_inode (trans=0xde16db20, dip=0xe47032d0,
      obj_id=180316461440, asof=18446744073709551615, localization=131072,
      flags=0, errorp=0xde16da68)
      at /home/source/dragonfly/current/src/sys/vfs/hammer/hammer_inode.c:376
  #5  0xc026fc95 in hammer_vop_nresolve (ap=0xde16db78)
      at /home/source/dragonfly/current/src/sys/vfs/hammer/hammer_vnops.c:924
  #6  0xc01ee2d4 in vop_nresolve_ap (ap=0xde16db78)
      at /home/source/dragonfly/current/src/sys/kern/vfs_vopops.c:1613
  #7  0xde35b032 in ?? ()
	:

  (kgdb) p *type
  $10 = {ks_next = 0xc416ff50, ks_memuse = {55452800, 51921920,
      0 <repeats 14 times>}, ks_loosememuse = 107374720, ks_limit = 107374182,
    ks_size = 0, ks_inuse = {86645, 81128, 0 <repeats 14 times>},
    ks_calls = 1694049, ks_maxused = 0, ks_magic = 877983977,
    ks_shortdesc = 0xc02f039d "HAMMER-inodes", ks_limblocks = 0,
    ks_mapblocks = 0, ks_reserved = {0, 0, 0, 0}}