Network interface RUNNING and UP flags
Coleman
cokane at cokane.org
Mon Aug 9 13:47:48 PDT 2004
Here, I pushed that section of code up before the prior
mtx_unlock(&tp->tap_mtx) above it, then removed the splimp/splx calls.
Is this what you were referring to (attached)? Also, I noticed splx and
splimp are called in a number of other places in this driver, even under
-CURRENT. You want those out too? The patch is a patch on the original
-CURRENT version of the driver and not a patch to the previous patch I
received.
--
coleman kane
On Sat, 2004-08-07 at 05:23, Yar Tikhiy wrote:
> On Sat, Aug 07, 2004 at 10:06:17AM +0300, Alex Lyashkov wrote:
> >
> > not better move this under tp->tap_mtx mutex without using splX
> > functions?
>
> ...especially taking into account that splX do nothing
> in CURRENT anyway. Mutex locking framework adopted by
> the interface driver should be used of course.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: if_tap.c.diff
Type: text/x-patch
Size: 487 bytes
Desc:
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20040809/c5910250/if_tap.c.bin
More information about the freebsd-hackers
mailing list