Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Oct 2002 22:18:45 +0200
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        freebsd-arch@FreeBSD.ORG
Subject:   Re: when will malloc(9) be giant-free? 
Message-ID:  <39165.1034713125@critter.freebsd.dk>
In-Reply-To: Your message of "Tue, 15 Oct 2002 14:45:13 EDT." <15788.25145.767671.511786@grasshopper.cs.duke.edu> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <15788.25145.767671.511786@grasshopper.cs.duke.edu>, Andrew Gallatin
 writes:
>
>I'm trying to call malloc from a mostly giant-free driver, and dying
>like this:
>
>panic(c0346b0e,c0346c57,c03584e6,138,c037caa0) at panic+0x11f
>_mtx_assert(c037cc60,1,c03584e6,138,158) at _mtx_assert+0xbc
>kmem_malloc(c0832078,21000,1,d8e287ec,c02db8ea) at kmem_malloc+0x2d
>page_alloc(0,21000,d8e287df,1,23459e4) at page_alloc+0x27
>uma_large_malloc(21000,1,c02db064,6,c4435cfc) at uma_large_malloc+0x5a
>malloc(20fff,c037af20,1,d8e2883c,c4741873) at malloc+0xcd
>__gm_arch_kernel_malloc(20fff,0,d8e2884c,c47435d1,20fff) at __gm_arch_kernel_malloc+0x12
>[...]
>Yes, I whined about this a few months ago in relation to mbuf allocation
>at interrupt time (I was porting the ethernet emulation side of our
>driver to -current).

/me clears his throat and puts a bass-voice on the choir.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39165.1034713125>