Andrew Gallatin wrote:
Paul Durrant writes:
> calling read()). The issue is that the application may call read at
> any time so your buffer may not be freed back to the driver for a long
> time, and crucially your buffer may not have been freed back to the
> driver before detach(9e) is called. You *must* therefore keep track of
Excellent response. If you want to test an example of this, run any
sort of client/server TCP streaming benchmark (netperf, iperf, etc)
where the receive side is coming across your driver, and use a large
TCP window size. Then suspend the server side of the benchmark
while traffic is still flowing. Then try to remove your driver.
The system should not panic :)
Yes, it's another our regular test case for NIC drivers. :-)
--
Cheers,
----------------------------------------------------------------------
Oliver Yang | [EMAIL PROTECTED] | x82229 | Work from home
_______________________________________________
networking-discuss mailing list
[EMAIL PROTECTED]
