From owner-freebsd-current@FreeBSD.ORG  Fri Feb 20 15:46:39 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 5FB7416A4CE
	for <current@FreeBSD.org>; Fri, 20 Feb 2004 15:46:39 -0800 (PST)
Received: from green.homeunix.org (green@localhost [127.0.0.1])
	by green.homeunix.org (8.12.10/8.12.9) with ESMTP id i1KNkcHS013949
	for <current@FreeBSD.org>; Fri, 20 Feb 2004 18:46:38 -0500 (EST)
	(envelope-from green@green.homeunix.org)
Received: from localhost (green@localhost)i1KNkbkI013945
	for <current@FreeBSD.org>; Fri, 20 Feb 2004 18:46:38 -0500 (EST)
Message-Id: <200402202346.i1KNkbkI013945@green.homeunix.org>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: current@FreeBSD.org
From: Brian Fundakowski Feldman <green@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 20 Feb 2004 18:46:36 -0500
Sender: green@green.homeunix.org
Subject: Testers wanted: reentrant resolver
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2004 23:46:39 -0000

New and improved, my reentrant resolver patch even includes documentation!
What does it do, you ask?  Why, it simply makes tabbed browsing in Mozilla 
an order of magnitude faster!  How does it do that, you ask?  Well, it 
simply makes h_errno and the getaddrinfo(3)/getipnodebyname(3) functions 
thread-safe in a more intelligent way.  There is still a global lock around 
some pieces of data, but for the most part the global lock (which is what 
serialized EVERY hostname lookup in threaded programs) is not contested.  
It's still used for some NIS-related tasks, looking up hostents, and looking 
up server port names, but that's not comparatively very important.  The 
resolver itself is a thread-safe backend where each thread gets its own 
resolver that can run concurrently with the rest, so the time spent blocked 
waiting for DNS responses is gone.

Give it a try, and let me know how it works!
<URL:http://green.homeunix.org/~green/reentrant_resolver.patch>

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\