Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, 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 - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
