From owner-freebsd-net@FreeBSD.ORG Wed Mar 14 12:31:22 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63F2016A401 for ; Wed, 14 Mar 2007 12:31:22 +0000 (UTC) (envelope-from keith.arner@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id E75C213C465 for ; Wed, 14 Mar 2007 12:31:21 +0000 (UTC) (envelope-from keith.arner@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so182202nfc for ; Wed, 14 Mar 2007 05:31:20 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=tNvDCWClTOb+q6x5PIjMUHN4mvupcjnDaQ2PPhsA/9xye8nT2nlBdTDwJludmUnEoADjkr57ygum8JVHfJfCXK7GNGkWJzF8FONAE3arsmOPkp1jOQIYpJIJcb8PBCTlHq6BFhuszJcYOJNWs0c2EgWy+qsaKU9EIShfdVzenSM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=l8WAvOgFmp/nL5kUjv5GCMeU431EqHlDnaJMmrecR3JLBJWXvCfeRCKabi6iWAzAky+mwYFBQmPbaI5bmImo67kNSpDOiIJMdPQ93RN416FwQUf5cMgdWYhMKC9qpJXDpBR9hSL11wiJNS0DKNfS+yR7l3qn0tNJlJyDc/LKb54= Received: by 10.78.164.9 with SMTP id m9mr1146827hue.1173875480629; Wed, 14 Mar 2007 05:31:20 -0700 (PDT) Received: by 10.82.121.1 with HTTP; Wed, 14 Mar 2007 05:31:20 -0700 (PDT) Message-ID: <8e552a500703140531l39f6fae5o518ee271b879eb1a@mail.gmail.com> Date: Wed, 14 Mar 2007 08:31:20 -0400 From: "Keith Arner" Sender: keith.arner@gmail.com To: "Robert Watson" In-Reply-To: <20070311073249.R20646@fledge.watson.org> MIME-Version: 1.0 References: <45C0CA5D.5090903@incunabulum.net> <45E6BEE0.2050307@FreeBSD.org> <45E6C22D.7060200@freebsd.org> <45E6D70C.10104@FreeBSD.org> <45EEB086.3050409@FreeBSD.org> <45F03269.7050705@FreeBSD.org> <45F08F1D.5080708@us.fujitsu.com> <20070310035135.B30274@fledge.watson.org> <8e552a500703102157p1845926au65bb3adaf81c01c0@mail.gmail.com> <20070311073249.R20646@fledge.watson.org> X-Google-Sender-Auth: bc3f232510bb6fcc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: net@freebsd.org Subject: Re: netisr_direct X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2007 12:31:22 -0000 On 3/11/07, Robert Watson wrote: > > > Yes -- right now the in-bound TCP path is essentially serialized because > of > the tcbinfo lock. The reason for this is that the tcbinfo lock doesn't > just > protect the inpcb chains during lookup, but also effectively acts as a > reference to prevent the inpcb from being freed during input processing. > There are several ways we could start to reduce contention on that lock: > So, why is the tcbinfo lock being used to protect the pcb from deletion? Why isn't the INP_LOCK on the pcb used, instead? Keith -- Well, I didn't find the Holy Grail, but I did find a rusty cup without too many holes in it... -- Jeff Semke