Date: Fri, 24 Sep 2004 14:08:55 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Waldemar Kornewald <Waldemar.Kornewald@web.de> Cc: FreeBSD-net <freebsd-net@freebsd.org> Subject: Re: locking & iovecs Message-ID: <Pine.NEB.3.96L.1040924140758.82478K-100000@fledge.watson.org> In-Reply-To: <4153B897.9040807@web.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Sep 2004, Waldemar Kornewald wrote: > > Once GIANT is really gone, it may be nearly that easy. We're a ways > > from that though. > > So, the code is not fully thread-safe yet (we want to drop GIANT)? Then, > I misunderstood something. Will 5.3 be freed of GIANT? Including some components in the kernel will force the Giant lock back over the network stack. For example, if you compile with KAME IPSEC or IPX. There is active work in many of those areas to remove that requirement. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040924140758.82478K-100000>