Date: Mon, 18 Jan 1999 13:55:17 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT Message-ID: <Pine.BSF.3.95.990118135408.8525R-100000@current1.whistle.com> In-Reply-To: <199901182141.IAA14501@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Jan 1999, Bruce Evans wrote: > >There was some talk about the fact that malloc(..M_CANWAIT) > >can now return with a failure. > > You mean M_WAITOK. yes.. a braino.. (I corrected in later mail) > > >Is that true? > > Of course not. It is fundamental that malloc(..., M_WAITOK) either > succeeds or panics. Most callers depend on this and don't check for > success. The others are bogus. actually it turns out to be true.. see other email from matt. > > You may be thinking of the documented but unimplemented new flag > M_ASLEEP. It's hard to see what this does (since it is > unimplemented), but the docs say to only use it with M_NOWAIT. Unrelated > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.3.95.990118135408.8525R-100000>