Date: Thu, 27 May 1999 16:37:25 -0400 From: Dennis <dennis@etinc.com> To: Mike Smith <mike@smith.net.au> Cc: hackers@freebsd.org Subject: Re: mbuf stuff Message-ID: <199905272140.RAA04730@etinc.com> In-Reply-To: <199905271926.MAA01660@dingo.cdrom.com> References: <Your message of "Thu, 27 May 1999 11:39:11 EDT." <199905271642.MAA03346@etinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:26 PM 5/27/99 -0700, you wrote: >> >> We've encountered a situation where mbuf allocations inside a device >> interrupt handler fails occasionally...and it always seems to happen when >> rtalloc() is interrupted. Is this due to some sort of locking (rtalloc is >> run at splnet())...should it perhaps be run at splimp() to avoid this problem? > >It sounds like your device's interrupt handler should be in the 'net' >mask; you certainly shouldn't be doing anything that manipulates mbufs >in a non-'net'-masked interrupt handler. Well how does one check/set this? > >> What other causes for mbuf failures might reasonably be expected? Is >> allocating mbufs at interrupt time something that wasnt expected in the >> original system design? > >The mbuf pool might be empty. This one I figured out :-) Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905272140.RAA04730>