From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 10:46:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8976416A4D0 for ; Wed, 17 Nov 2004 10:46:45 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3911943D2F for ; Wed, 17 Nov 2004 10:46:45 +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 iAHAjGo7071185; Wed, 17 Nov 2004 05:45:16 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAHAjGAI071182; Wed, 17 Nov 2004 10:45:16 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 17 Nov 2004 10:45:16 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <22756.1100683081@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: [HEADSDOWN] I'm done for now. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 10:46:45 -0000 On Wed, 17 Nov 2004, Poul-Henning Kamp wrote: > Giant is now pushed down through select/poll/ioctl. > > Please test and report problems. Great! This should hopefully both reduce contention on Giant in interesting cases (such as select-intensive socket stuff), as well as reduce the overal number of locking operations for some interesting paths (i.e., select on sockets, which previously paid the cost of locking/unlocking Giant but didn't need it). FWIW, I would not be surprised if we see some bug reports come in now that ioctl() is being run without Giant for the network stack back default. While some of those ioctl's are already running without Giant due to sharing code paths with set/getsockopt() and internal use of ioctl in the kernel, others have probably not seen as much exposure. Likewise, while the pipe ioctl code should be MPSAFE (and is pretty innocuous), that's not been confirmed. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research