From owner-freebsd-current Tue May 28 23:19: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4B19637B403 for ; Tue, 28 May 2002 23:19:04 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g4T6HxQW010400; Wed, 29 May 2002 08:17:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Terry Lambert , Richard Wenninger , current@FreeBSD.org Subject: Re: UMA lock In-Reply-To: Your message of "Tue, 28 May 2002 23:15:40 PDT." <20020529061540.88CD6380A@overcee.wemm.org> Date: Wed, 29 May 2002 08:17:59 +0200 Message-ID: <10399.1022653079@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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