Date: Wed, 29 May 2002 08:17:59 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Peter Wemm <peter@wemm.org> Cc: Terry Lambert <tlambert2@mindspring.com>, Richard Wenninger <richard@richardw.net>, current@FreeBSD.org Subject: Re: UMA lock Message-ID: <10399.1022653079@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 28 May 2002 23:15:40 PDT." <20020529061540.88CD6380A@overcee.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 condition >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... -- 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-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10399.1022653079>