Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Aug 2004 16:00:24 -0400
From:      Coleman <cokane@cokane.org>
To:        Yar Tikhiy <yar@comp.chem.msu.su>
Cc:        Alex Lyashkov <shadow@psoft.net>
Subject:   Re: Network interface RUNNING and UP flags
Message-ID:  <1092081623.65806.3.camel@schemer>
In-Reply-To: <20040807092347.GB39835@comp.chem.msu.su>
References:  <346a8022040806145018a5e18@mail.gmail.com> <1091862376.7840.3.camel@berloga.shadowland> <20040807092347.GB39835@comp.chem.msu.su>

next in thread | previous in thread | raw e-mail | index | archive | help
Seems to work in both -RELEASE and -CURRENT, though I needed to manually
apply the patch as line numbers were off in -RELEASE. I can see how the
locking could become a problem in -CURRENT.

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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1092081623.65806.3.camel>