From owner-freebsd-current@FreeBSD.ORG  Sat Jul 30 22:32:51 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-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 A929216A421
	for <freebsd-current@freebsd.org>; Sat, 30 Jul 2005 22:32:51 +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 5015C43D45
	for <freebsd-current@freebsd.org>; Sat, 30 Jul 2005 22:32:51 +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 EAC4CBC66;
	Sat, 30 Jul 2005 22:32:49 +0000 (UTC)
To: Julian Elischer <julian@elischer.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sat, 30 Jul 2005 15:31:40 PDT."
	<42EBFFCC.5010603@elischer.org> 
Date: Sun, 31 Jul 2005 00:32:49 +0200
Message-ID: <6843.1122762769@phk.freebsd.dk>
Sender: phk@phk.freebsd.dk
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
	Brian Candler <B.Candler@pobox.com>
Subject: Re: Apparent strange disk behaviour in 6.0 
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: Sat, 30 Jul 2005 22:32:51 -0000

In message <42EBFFCC.5010603@elischer.org>, Julian Elischer writes:

>> Look at your scheduler...
>
>I plan on doing just that..

Because of the two pusher threads, GEOM is very sensitive
to scheduler issues.

-- 
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.