:In 4.3, the code was able to deal with cluster allocation failing. We
:have a somewhat different situation now, because many network
:interface devices have less-flexible DMA mechanisms which don't allow
:packet reception into non-contiguous buffers, so we need to have at
:least a certain number of clusters available for this purpose.
:
:-GAWollman
:
:--
:Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
This is an interrupt level mechanism. The mbuf code is *already* allowed
to (and does) return NULL in this case so I don't think it applies to
the problem under discussion.
The case that is causing the panics is with the non-interrupt mbuf
allocation mechanism. Specifically, the case where M_WAIT is used.
The second problem under discussion, which really ought to be separated
out from the mbuf panic problem, is the potential for a deadlock or
denial of service attack when the system is attacked in a manner that
eats all available mbufs.
:[EMAIL PROTECTED] | O Siem / The fires of freedom
:Opinions not those of| Dance in the burning flame
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
