Date: Mon, 25 Oct 2004 12:22:21 -0500 (EST) From: Sam <sah@softcardsystems.com> To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-arch@freebsd.org Subject: Re: 6.0 Witness squawk Message-ID: <Pine.LNX.4.60.0410251215290.29901@athena> In-Reply-To: <xzpk6tedbrc.fsf@dwp.des.no> References: <Pine.LNX.4.60.0410251037540.29901@athena> <Pine.LNX.4.60.0410251126010.29901@athena> <xzpk6tedbrc.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> Sam <sah@softcardsystems.com> writes: >> There are three entry points into the driver. 1) The disk >> layer 2) the netisr routine 3) the rexmit timer. > > AFAIK, if the code that calls malloc() can be reached from 2) or 3), > you're not allowed to use M_WAITOK. Hm. If that's true then I've either got to petition you fellas to change disk_alloc(), disk_create(), and disk_destroy() to use M_NOWAIT or schedule a callback where these calls can be handled properly. Thoughts about either approach? Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.60.0410251215290.29901>