From owner-freebsd-current@FreeBSD.ORG  Fri Jul 15 06:57:02 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
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 DFF6F16A41F;
	Fri, 15 Jul 2005 06:57:02 +0000 (GMT)
	(envelope-from phk@phk.freebsd.dk)
Received: from haven.freebsd.dk (haven.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 836C143D53;
	Fri, 15 Jul 2005 06:57:02 +0000 (GMT)
	(envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (unknown [192.168.48.2])
	by haven.freebsd.dk (Postfix) with ESMTP id AE3D9BC83;
	Fri, 15 Jul 2005 06:57:00 +0000 (UTC)
To: Scott Long <scottl@samsco.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 15 Jul 2005 00:45:24 MDT."
	<42D75B84.7090601@samsco.org> 
Date: Fri, 15 Jul 2005 08:57:00 +0200
Message-ID: <8524.1121410620@phk.freebsd.dk>
Sender: phk@phk.freebsd.dk
Cc: Poul-Henning Kamp <phk@haven.freebsd.dk>, s223560@studenti.ing.unipi.it,
	Robert Watson <rwatson@freebsd.org>, current@freebsd.org,
	Luigi Rizzo <rizzo@icir.org>
Subject: Re: location of bioq lock 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 15 Jul 2005 06:57:03 -0000

In message <42D75B84.7090601@samsco.org>, Scott Long writes:

>I agree.  The 'side queue' can be a bioq also that gets handed off in
>whole to the driver once the path is unfrozen, but that's an
>optimization that is best done at a later time.

It's hardly worth the effort I think.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.