On Tue, Jun 18, 2002 at 10:36:36PM -0600, Kenneth D. Merry wrote:
> I've released a new zero copy sockets snapshot, against -current from June
> 18th, 2002.
> The fixes that went into this snapshot:
> - Take mutex locking out of ti_attach(), it isn't really needed.
> As long as we can assume that probes of successive ti(4) instances
> happen sequentially, we'll be safe in doing this. Thanks to John
> Baldwin for pointing out the solution to that problem. (The lock in
> ti_attach() was causing all sorts of WITNESS warnings when
> bus_setup_intr() was called.)
> - Added a new routine, vm_object_allocate_wait(). This is a variant of
> vm_object_allocate() that allows the user to specify whether the
> uma_zalloc() call inside vm_object_allocate_wait() is called with
> M_WAITOK or M_NOWAIT. This eliminates a WITNESS warning caused when
> jumbo_vm_init() calls vm_object_allocate() with the jumbo lock held, and
> potentially gives other callers the option of eliminating the mandatory
> wait on the uma_zalloc() call.
I think this problem was fixed in recent -CURRENT by JeffR. Notably,
the VM system should not allow itself to recurse on itself when called
> (vm_object_allocate() now just calls vm_object_allocate_wait() with the
> proper argument.)
> With those fixes, plus several fixes that have gone into -current over the
> past week or so, the zero copy sockets code runs without any WITNESS
> warnings at all now.
> Kenneth Merry
> [EMAIL PROTECTED]
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message