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 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
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message