Date: Wed, 29 May 2002 00:07:09 -0700 From: Peter Wemm <peter@wemm.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Terry Lambert <tlambert2@mindspring.com>, Richard Wenninger <richard@richardw.net>, current@FreeBSD.org Subject: Re: UMA lock Message-ID: <20020529070709.03852380A@overcee.wemm.org> In-Reply-To: <10399.1022653079@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote:
> In message <20020529061540.88CD6380A@overcee.wemm.org>, Peter Wemm writes:
>
> >As you said, _sleeping_ is the problem. M_WAITOK means "you may sleep if
> >you like". ie: it is a time bomb waiting for the right low memory conditio
n
> >which will then explode with a 100% authentic crash or lock up.
> >
> >Pretend it said M_SLEEPOK instead of M_WAITOK.
>
> Uhm, I'm actually seeing the opposite behaviour as well: after I
> changed the md(4) driver to use M_NOWAIT I still see malloc/zalloc
> sleeping...
No, this is a bug in UMA. In certain circumstances, it calls itself
with M_WAITOK even when it itself was called with M_NOWAIT.
Cheers,
-Peter
--
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020529070709.03852380A>