From owner-freebsd-net@FreeBSD.ORG Fri Sep 24 18:09:41 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9DD216A4CE for ; Fri, 24 Sep 2004 18:09:41 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A69A43D4C for ; Fri, 24 Sep 2004 18:09:41 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i8OI8tu3099792; Fri, 24 Sep 2004 14:08:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i8OI8trY099789; Fri, 24 Sep 2004 14:08:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 24 Sep 2004 14:08:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Waldemar Kornewald In-Reply-To: <4153B897.9040807@web.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD-net Subject: Re: locking & iovecs X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 18:09:41 -0000 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